-
Notifications
You must be signed in to change notification settings - Fork 565
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
no timeout on client.PullImage #802
Comments
Oh interesting, this sounds like a bug. Thanks for reporting! I'm able to reproduce it with
I'll investigate why the |
So the issue is that the client doesn't get to the code that handles the InactivityTimeout because it applies only to reads of the body and in this case the server accepts the connection, takes the request but doesn't respond. This will take a little longer to fix, but you could use a context to workaround this issue, making a call that should return quickly using a short timeout (for example, |
great to hear that you could reproduce it instantly. As you plan to fix it I will not touch the docker remote API code and wait for your fix here.
|
Situation:
I have a docker daemon running under CoreOS and exposed the TCP port by creating and binding a TCP socket (as described in the docs https://coreos.com/os/docs/latest/customizing-docker.html)
I have the situation that in some cases the server config (using Ignition) fails and the docker daemon does not start up, but the socket on port 2375 is reachable.
When calling now
client.PullImage
the request stays hanging at that point.I tried to pass
InactivityTimeout
but without result.Is there some other way to pass some timeout to the PullImage call?
thx & cheers
Heiko
The text was updated successfully, but these errors were encountered: