storage: keep the resolver's address family order when dialing blob front-ends - #53
Merged
Merged
Conversation
luke-lombardi
force-pushed
the
ll/blob-dial-fallback
branch
from
September 26, 2026 16:25
bdb1405 to
38086c8
Compare
…ront-ends The dialer shuffled every resolved address together, so on a host with an IPv6 default route it cannot use (router advertisement, ULA addresses only) an IPv6 address picked first waited out the 10s dial timeout. One Docker Hub layer took two such timeouts before a 315ms transfer.
luke-lombardi
force-pushed
the
ll/blob-dial-fallback
branch
from
September 26, 2026 16:28
38086c8 to
5d15d99
Compare
luke-lombardi
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The blob range dialer shuffles every resolved address together, so on a host with an IPv6 default route it cannot use (router advertisement, ULA addresses only, as on our bare-metal agent nodes) an IPv6 address picked first waits out the 10s dial timeout. A 58 MB Docker Hub layer took two such timeouts before a 315ms transfer; curl -6 to registry-1.docker.io hangs on those nodes while curl -4 connects in 40ms. Keep the resolver's family order (RFC 6724) and shuffle within it.