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
Set idle timeouts for HTTP reads and writes in communications with a registry #19743
Conversation
…e registry Otherwise, some operations can get stuck indefinitely when the remote side is unresponsive. Fixes moby#12823 Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>
e305301
to
84b2162
Compare
cc @docker/distribution-maintainers |
LGTM |
LGTM |
1 similar comment
LGTM |
@aaronlehmann @dmcgowan is this for 1.10 ? |
@tiborvass: I'm not completely sure. This is a common user frustration that we wanted to fix in 1.10, and I would have submitted the PR much earlier if I had realized the problem still existed. I know we are getting late in the release cycle so I'm not sure whether it's too late. |
It's green so, let me merge |
Set idle timeouts for HTTP reads and writes in communications with a registry
@aaronlehmann @tiborvass adding more stability is a good thing; Is there any risk in this change? Guess that would be the deciding factor |
I think it's pretty low risk. |
Added impact/changelog as a notable bug fix for #12823 |
This was reverted in #19971 |
Otherwise, some operations can get stuck indefinitely when the remote
side is unresponsive.
Fixes #12823