Timeline for docker-compose up/down just one container
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 21, 2021 at 12:49 | comment | added | Nusrat Nuriyev | ... "by having a separate .yml file." Yes, it's not an ideal solution but it deletes not only volumes but also a network, which "docker-compose rm -s -v yourService" won't do, according to what I understand. | |
| Dec 11, 2019 at 12:02 | comment | added | greenoldman |
And where do you specify the container you would like to get up/down? -f is the selector of compose file, not container.
|
|
| Sep 17, 2017 at 18:20 | comment | added | icarito |
You can do docker-compose -f docker-compose-production.yml down
|
|
| Sep 15, 2017 at 10:17 | comment | added | Jordan Morris |
How does this work when it comes time to do docker-compose down? Wouldn't it bring down all the containers which have been brought up in all .yml files?
|
|
| May 22, 2017 at 17:21 | vote | accept | Inquisitor Shm | ||
| May 22, 2017 at 17:04 | review | Late answers | |||
| May 22, 2017 at 17:06 | |||||
| May 22, 2017 at 16:59 | review | First posts | |||
| May 22, 2017 at 19:13 | |||||
| May 22, 2017 at 16:46 | history | answered | icarito | CC BY-SA 3.0 |