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 daemon hang for futex #42921
Comments
3.10.0-1062 is known to have kernel memory leak, easily reproduced via frequently restarting containers. |
@zq-david-wang okay, I have searched the
|
I do not see memory error log in the file you attached. Strange thing is the timestamp, the last line ' s timestamp |
@zq-david-wang I use the command ``ps -aux | awk '$8 == "D"', return nothing, don't find process stuck in "D" state, is there any other reason? in addition , I search all log about dockerd, find a warning message:
is it a possible reason? but I have changed the configurition successful before the time
|
Any chance that this runc 1.0.0-rc93 bug opencontainers/runc#2871 would be relevent?
If the singature matches, you could upgrade your docker. To simplily fix the runc issue:
|
Hi, I have similar problem on my GitLab Runners.
https://gist.github.com/pawcykca/2e4fc245a08e7ee62ccdd26233870ad4
https://gist.github.com/pawcykca/292ec81a8810136e957f1ded6a72c172
https://gist.github.com/pawcykca/7c2bf80127e7c0f0d53672fb6ce4d040
Any ideas what is the root cause? |
I encounter this today and i can reproduc into a lab.
we use docker 20.10 on the impacted docker host
|
Description
Hi team, I met a problem that docker daemon hang on futex, which unlike #25321; #28754
Steps to reproduce the issue:
strace
, see below:2.debug the docker, dump the goroutine stacks which use
kill -SIGUSR1 $(pidof dockerd)
goroutine-stacks-2021-10-08T153230+0800.log
3.use pprof check the groutine, find some mutex, for example:
the details:
goroutine.log
Describe the results you received:
can't use the command
docker rm -f
、docker run -it
etc.Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
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: