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
Exposing sentry service in docker-compose file
Yesod and docker-compose logs in development mode
Docker compose to always deploy using latest image
JHipster - Doubts in the development using Microservices Architecture
Gogs + Drone getsockopt: connection refused
Concourse result keeps loading
Docker-compose: AttributeError: 'module' object has no attribute 'ssl'
scaling a service with docker compose
Docker Compose apparently ignores COMPOSE_FILE
Where does Docker install gems on a mac
What is the difference between docker-machine and docker-compose?
Docker Compose port issue. Cannot launch docker project on localhost
Name an image built from running a docker-compose file
Race conditions after changing names in docker-compose.yml
Docker compose - image not found
How to work out the hostname that compose gives containers?