Login refactor (small breakout): hostsstore resolution cleanup#3410
Conversation
As described in containerd#3047, hosts.toml file lookup will treat https://foo:443 and https://foo differently, possibly leading to divergent behaviors *for the same registry*. This PR makes it so that a registry URL using the default https port (443) will ALSO lookup files stored in a "portless" directory. Finally, as dockerconfigresolver.go will soon go under significant changes, the hosts.toml resolution functions have been also isolated in their separate, own file. Signed-off-by: apostasie <spam_blackhole@farcloser.world>
a49487d to
1a4a5a9
Compare
|
CI failure appears to be a network fluke. |
|
Gentle ping on this. |
|
@apostasie @AkihiroSuda This may have broken repository authentication (currently not able to confirm due to lack of time). When doing EDIT: I'm using v2.0.0-rc.2, but maybe this change is not yet merged there? In that case, the issue is related to something else (perhaps some issue mentioned in #3072 ). |
|
@nakamorichi will look asap tomorrow. |
|
@nakamorichi confirming this change here has not made it to any rc. thanks |
|
@nakamorichi (works as well with private repositories) If you are still facing issues, as suggested, you should open a new ticket, with details on what exactly you are doing / how to reproduce. |
|
@apostasie Understood. I'll see if I can find a way to reproduce it. Btw, I'm using lima on macOS Sequoia, but I'm not sure how it could have impact in this case. |
Am on Lima too (and whatever is macOS latest). |
Fix #3047
Commit message for details.
This is not testable yet (IIRC, because of the way we currently resolve authentication), but I will add tests for this specific condition later on in another upcoming "login" PR.