How does docker-compose manage containers

This article mainly explains "how docker-compose manages containers". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn how to manage containers with docker-compose.

Taking the laradock environment as an example, we introduce the operation of docker-compose. All commands need to be run under the laradock folder in command line mode.

View existing or running containers

Docker-compose ps

Stop all running containers, but do not delete containers

Docker-compose stop

Stop and delete the running container

Docker-compose down

View nginx's log

Docker-compose logs nginx

Delete all containers

Docker rm `docker ps-a-q`

Delete all mirrors

Docker rmi `docker images-q`

Delete all unused mirrors in docker-compose

Docker image prune

Delete all existing mirrors

Docker image prune-- force-- all or docker image prune-f-a

Delete all stopped containers

Docker container prune

Thank you for your reading, the above is the content of "how docker-compose manages containers". After the study of this article, I believe you have a deeper understanding of how docker-compose manages containers, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!