-
Notifications
You must be signed in to change notification settings - Fork 116
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
Daemon locks up when running large number of containers #3186
Comments
Hi, were you able to figure out a fix for this? I'm getting the same issue, docker just crashes unexpectedly while either running or building a container. My stacktrace is nearly identical to yours. |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
This is still happening with the latest release and I've uploaded diagnostics regularly on my issue to keep it alive: |
Yeah, it's still happening for me too, though less frequently. Other than having a high workload I can't work out what's causing it. |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Expected behavior
docker daemon and tools continue to run and respond
Actual behavior
network connections to the docker vm seem to hang for ever or timeout with no response.
connecting to the TTY via screen doesn't respond.
My only solution is to run
Restart
from the menu and try again.Information
I haven't worked out what reproduces it other than running a demanding (for a small laptop) workload.
I have a few postgres instances, single node kafka cluster (1 kafka & 1 zookeeper instance) and a few small microservices.
It usually happens just after I start some new component that everything. locks up. I've had the problem multiple times over versions released in the last few months, I've tried the
stable
release and seen it happen but I'm usually running theedge
release.Diagnostic logs
Diagnose didn't print anything extra out other than
Diagnose succeded
(succeeded spelt wrong btw) usually there is more information, so perhaps it wasn't responding either.Steps to reproduce the behavior
wurstmeister/zookeeper:351aa00d2fe9
wurstmeister/kafka:1.1.0
cassandra:3.9
)docker ps
I think similar issues might be:
I did get this crash while trying to get all the information for this report
The text was updated successfully, but these errors were encountered: