Increase docker registry client timeout #5674
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jurre
reviewed
Sep 11, 2022
jurre
approved these changes
Sep 11, 2022
jeffwidman
approved these changes
Sep 12, 2022
pavera
force-pushed
the
pavera/increase-docker-timeout
branch
from
ec42ba7 to
cb05dd6
Compare
Co-authored-by: Jurre <jurre@github.com>
pavera
force-pushed
the
pavera/increase-docker-timeout
branch
from
cb05dd6 to
8b4a661
Compare
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DockerRegistry2 has a default read timeout of 5s. We have seen issues where loading the list of docker tags times out if that list is very large. This increases the timeout to 10s which in my testing locally is sufficient to load hexpm/elixir with > 150k tags.