-
Notifications
You must be signed in to change notification settings - Fork 134
Example creates hanging container #489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This ended up being something that was highly customized in my environment. Never the less, below are updated configs for using the latest and greatest versions of EFK. All versions compatibilities provided are confirmed working. There are some minor different like volume mappings from the original documentation to my environment. Also the Dockerfile
fluent.conf
elasticsearch.yml
docker-compose.yaml
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 thefluentd
container first.If the
fluentd
container gets removed before theweb
container, theweb
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.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
The text was updated successfully, but these errors were encountered: