Certainly! Below is a cheat sheet with common Docker commands and tasks related to interacting with your containerized application:
-
Build and Start Containers:
docker-compose up --build
-
Stop Containers:
docker-compose down
-
View Container Logs:
docker-compose logs [service_name] # Example: docker-compose logs frontend -
Access Container Shell:
docker exec -it [container_name_or_id] /bin/sh # Example: docker exec -it hand_off-frontend-1 /bin/sh
- Access PostgreSQL Shell:
docker exec -it hand_off-postgres-1 psql -U matt -d handofftest
-
List Docker Images:
docker images
-
Remove Unused Images:
docker image prune
-
List Docker Volumes:
docker volume ls
-
Remove Unused Volumes:
docker volume prune
-
List Docker Networks:
docker network ls
-
Inspect a Docker Network:
docker network inspect [network_name] # Example: docker network inspect handoff_network
-
Access Frontend:
- Local: http://localhost:5173/
- Docker Network: http://172.19.0.4:5173/
-
Access API:
- Local: http://localhost:8000/
- If you make changes to your code, restart the containers using
docker-compose downanddocker-compose up --build. - When troubleshooting, check the logs for each service using
docker-compose logs [service_name].
Feel free to adjust the commands based on your specific container names, service names, or preferences. If you encounter specific issues or need further assistance, let me know!