Closed ohthehugemanatee closed 7 years ago
I find this issue quite annoying as well, therefore I looked into the code to see if I could create some PR to fix this issue.
I found this LoC/comment. So apperently it used to shutdown the containers, but it didn't always work? Can we renable that feature, if it at least works most of time? Or did it never work?
Alternatively we could also introduce a new command, which shutsdown all containers created by dork. This should be possible, since we have the meta containers and labels, right?
What should the command be called? dork-compose shutdown
?
The best route would be fixing the comment @sepal pointed out. If an auxiliary project is not attached to any networks, it should be shut down. We need to find out why it didn't work all the time.
Auxiliary services will shut down now if no more projects require them.
After my last dork container has exited, I still get
There's no way to end these containers without a manual
docker stop
.