-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
strange errors when pull authentication fails #2710
Comments
I ran into this pulling from an insecure registry (full
Note in the above error message, the parsing of the However, if i supplied the
|
we were printing something like: (0x1840f00,0xc00041bba0) Closes: containers#2710 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
fixed as part of: #2911 |
Here I have an image in an internal registry, I've replaced all references in the output with
${image}
. It is a valid reference that I can pull if i drop the--creds u:p
. I'm using that to force on a pull authentication error.The error resulting is...very strange. What's the
(0x1882e00,0xc000a47f40)
? And then why do we later think the image is an invalid transport?The text was updated successfully, but these errors were encountered: