-
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 daemon panic #17625
Comments
@alexmac big thanks for the report |
Looks like the classic issue of handing an http request body without properly wrapping the closer. |
@stevvooe So what solution are you proposing? Wrapping |
@tonistiigi I am not sure. The "poisoned" reader needs to be tracked down and wrapped with closer that intercepts calls to closed resources. |
This panic appears to be related to 4dce280. There is a race betwee |
I'm experiencing a number of panics of the docker daemon with a self-compiled build of the 1.9 branch. I've not yet got any repro steps but here are the details incase the stack traces are enough to spot the bug. This was built from git commit 80439a4 and running on an up to date Amazon linux AMI:
docker info:
End of the docker log:
The text was updated successfully, but these errors were encountered: