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
Very long Docker run commands cause Docker to hang indefinitely #37525
Comments
wondering if this is specific to docker for mac (which uses a proxy to forward the local docker socket to the daemon running inside the LinuxKit vmware) Does this also reproduce if you run this from within a container that connects to the docker daemon through the socket (that way, not going through the proxy); The following command gives you an interactive container with the docker client inside it, connecting to the daemon inside the LinuxKit VM docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock docker:18.06 sh |
I was able to reproduce this on a Linux host:
|
I'm able to reproduce this behavior at HEAD of master from inside a development container. Here's the debug logging after running the script I've linked above:
The command hangs here. I ran the following in another shell:
|
ping @kolyshkin @mlaventure PTAL |
Description
Docker hangs when a very long
run
command is provided. It's possible that this is a result of a deadlock due to some STDERR buffer overflowing, and Docker never receiving theOCI runtime create failed
output it expects from the underlying OCI driver. This also prevents the daemon from being restarted properly.cc: @jmillikin-stripe
Steps to reproduce the issue:
Generated by:
Describe the results you received:
Docker hangs forever and the container remains in the
CREATED
state forever. Trying todocker inspect
,docker start
, ordocker rm
the created container hangs forever.Describe the results you expected:
Docker exits with the error message
file name too long": unknown..
or a similar error message identifying the length as being too long. No container should be created.Additional information you deem important (e.g. issue happens only occasionally):
I've confirmed this happens in
18.06.1-ce
of Docker for Mac and18.03.1-ce
of Docker for Linux.We suspect this is a deadlock related to a buffer overflow where something is overflowing a buffer that is set to 32kb.
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: