Description
Describe the bug
The docker container web
in the docker-compose example will zombie/hang and cause strange docker engine issues because of the dependency on the logging driver not existing if the stack decides to stop the fluentd
container first.
If the fluentd
container gets removed before the web
container, the web
containers gets zombified and can be stopped/killed by normal docker commands.
If anyone gets caught in this mess the easiest solution is to do the following which is generally not recommended but works:. Please note the last command will prune ALL docker containers, select the web
containers image specifically to have other containers unaffected.
systemctl restart docker.socket docker.service
docker rm -f <web container name>
docker container prune
I've previously not been very fond of docker's logging driver functionality, but I'm coming back around and giving it another try. If the logging driver doesn't exist the containers seem to hang. Is this typical? Is there something I'm missing?
Link to the problematic documentation
https://docs.fluentd.org/container-deployment/docker-compose
Expected explanation
compose up/down removes the stack properly
Additional context
No response