-
Notifications
You must be signed in to change notification settings - Fork 18.6k
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
docker stops responding on some machines #42386
Comments
Just to be sure; 20.10.2 is various patch releases behind the current release (20.10.6). If you have a test environment to reproduce; are you still able to reproduce this issue on the latest 20.10.6 release? |
I've reproduced this with an updated docker:
|
Hello, I still see this problem frequently. Anything I can do to start troubleshooting the cause? It seems to happen more often on machines that have more containers running. |
Description
The docker process on some of our machines seems to get in a bad state where many threads are blocked on mutexes. Some of the problems we see:
Steps to reproduce the issue:
Describe the results you received:
docker inspect hangs for some containers (not all)
DNS forwarding hangs; cannot resolve hostnames from within container
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
docker dump log attached. File is huge (64M) compared to same file on working machines (which is less than 1M):
curl --unix-socket /var/run/docker.sock http://./debug/pprof/goroutine?debug=2
docker_dump.log.gz
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: