-
Notifications
You must be signed in to change notification settings - Fork 3.8k
fix: disable tls on http #9269
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
fix: disable tls on http #9269
Conversation
|
Hi @vsiravar. Thanks for your PR. I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Signed-off-by: Vishwas Siravara <[email protected]>
e39ee2e to
bf07706
Compare
|
Wondering if this was intentional / by design to match the original behavior in docker, where explicitly enabling or disabling verify meant: enable TLS, but with/without tls-verify. So disabling /cc @dmcgowan perhaps you know if that was the original intent. |
|
@vsiravar Can you explain the bug in more detail? I know there is currently an issue we should probably fix where we shouldn't do the fallback when using a default port (for example don't try http on 443 or tls on 80). Not sure of the case you are describing here though. |
|
I get a 401 forbidden error when I try to push an image to a localhost docker registry using basic auth. The repro steps using nerdctl using version 1.6.2 This is an example from docker docs . This works okay when I change the go module dependency in nerdctl to 1.7.6 and also works fine with docker. I am out of my depth with docker's original behaviour but is it intentional to always enable TLS for localhost and have the cc @dmcgowan |
|
docker engine marks |
|
Since it works with 1.7.6, then I assume this change has to be the reason for a different behavior with 1.7.7: 7779ce6 |
|
I was able to go through the steps but was not able to reproduce with nerdctl 1.6.2. The only case I could reproduce this error message was deleting |
|
Thanks for trying out the repro steps. I can seem to consistently reproduce this error. My |
|
I think this suggests that it's not intentionally matching Docker behavior since http localhost always sets skipVerify: containerd/remotes/docker/config/hosts.go Lines 106 to 108 in 788f7f2
|
We could probably just remove the setting of |
Bug fix to disable tls when http and tls is not configured.