Open
Description
Description
This is meant to collect all issues impacting login or overall authn/authz
- TestLoginWithPlainHttp appears to be broken #3044
- Even when explicitly passing https, registry requests to localhost are downgraded to http #3046
- hosts.toml file resolution does not seem to account for default port being ommitted #3047
-
nerdctl loginshould warn about passing along an explicit scheme #3052 - nerdctl login used against a basic auth server will error in confusing ways after hammering the server #3068
- nerdctl login allows passing a username with a colon, which is forbidden by RFC 7617 #3069
- nerdctl login will save whatever credentials is being provided when a registry does NOT ask for authentication #3070
- Tests manipulating credentials are not properly isolated from one another #3071
- Login to docker.io failed. (
expected acArg to be "docker.io", got "registry-1.docker.io") #3245 - Add harbor to our integration testing suite? #3257
Unconfirmed / need assessment:
- Cannot pull image from private repository after successful login #920
- client certificates are not sent when using
nerdctl pull? #427 -
nerdctl pushinterop issue with Harbor registry #1675 - Cannot push to Azure ACR #2840
- nerdctl pull from private registry mirror is missing Authorization header #2844
- nerctl commit image couldn‘t push #3248
- nerdctl pull failed (
unexpected media type text/html) #3264 - Option --insecure-registry does not work with pull & push (
no route to host) #299
Steps to reproduce the issue
na
Describe the results you received and expected
na
What version of nerdctl are you using?
1.7.6
Are you using a variant of nerdctl? (e.g., Rancher Desktop)
None
Host information
No response