Why doesn't docker-compose 'down' take an optional [SERVICE…] argument?
docker-compose down does not have a [SERVICE...] argument. Per docker-compose down --help: Usage: down [options] I would like to be able to bring just one of my many containers down. I know that I can down a single container using docker down instead of docker-compose down, but I'm wondering why doesn't the docker-compose down command take an optional [SERVICE...] argument? All of the following docker-compose commands do take an optional [SERVICE...] argument: docker-compose build docker-compose create docker-compose kill docker-compose logs docker-compose pause docker-compose restart docker-compose rm docker-compose start docker-compose stop docker-compose unpause docker-compose up My docker-compose --version is 1.9.0
To stop a specific container use docker stop [OPTIONS] CONTAINERNAME [CONTAINERNAME...] You can find the list of currently active docker images by running docker ps
Disable autostart of docker-compose project
Docker-compose Error-Mean Stack Application won't get loaded with the data from mongodb container
docker-compose Windows volume
Trying to figure out why eslint-watch doesn't work with docker-compose correctly
docker-compose the latest stable version on ubuntu
docker compose environment variable for command
java.net.UnknownHostException: failed to resolve 'inventory-microservice'. Exceeded max queries per resolve 3
What does working_dir tag mean in a docker-compose yml file
If I upgrade an image in docker-compose, will its volumes be lost?
How to solve this docker-compose upgrading error?
Fabric Network - what happens when a downed peer connects back to the network?
Docker-compose and load balancing
Run arguments in Docker Compose
Docker compose file config
Systemd “No such file or directory” itself during “docker-compose up”
Docker compose yml static IP addressing