When you do docker-compose up
, it's based on a docker-compose.yml
file.
This usually brings up a network, builds and runs multiple services. If you do the up with the -d
flag, the docker-compose
client detaches and let the servers alone.
If you do a docker-compose down
, it shuts down the running containers and in addition removes the corresponding networks.
But... what if after the up
, the .yml
file has gone?
Question
Do you have to manually do the shutdown via docker stop
finding manually what are the services of that project, and docker rm
and docker network rm
and so on?
Or docker-compose
is intelligent enough to tag all the things (containers, nets, etc.) with a tag so you can tell it some thing like docker-compose down project-name
so it does not look in the .yml
(which is now not in the filesystem) file but inspecting the running instances and nets?