Skip to content
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

Closed
cgwalters opened this issue Mar 19, 2019 · 2 comments · Fixed by #2911
Closed

strange errors when pull authentication fails #2710

cgwalters opened this issue Mar 19, 2019 · 2 comments · Fixed by #2911
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@cgwalters
Copy link
Contributor

cgwalters commented Mar 19, 2019

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?

$ git describe --tags --always HEAD
v1.1.2-241-gac523cbe
$ ./bin/podman pull --creds u:p ${image}@sha256:bb6a76feac8852eae56a1f8bcdd0febee5f488f39a0c6e37b16d8e56e8e03e1e
WARN[0000] using rootless single mapping into the namespace. This might break some images. Check /etc/subuid and /etc/subgid for adding subids 
Trying to pull docker://${image}@sha256:bb6a76feac8852eae56a1f8bcdd0febee5f488f39a0c6e37b16d8e56e8e03e1e...ERRO[0000] Error pulling image ref //${image}@sha256:bb6a76feac8852eae56a1f8bcdd0febee5f488f39a0c6e37b16d8e56e8e03e1e: Error determining manifest MIME type for docker://${image}@sha256:bb6a76feac8852eae56a1f8bcdd0febee5f488f39a0c6e37b16d8e56e8e03e1e: unable to retrieve auth token: invalid username/password 
Failed

Error: error pulling image "${image}@sha256:bb6a76feac8852eae56a1f8bcdd0febee5f488f39a0c6e37b16d8e56e8e03e1e": Invalid image name "${image}@sha256:bb6a76feac8852eae56a1f8bcdd0febee5f488f39a0c6e37b16d8e56e8e03e1e", unknown transport "${image}@sha256"
@miabbott
Copy link
Contributor

I ran into this pulling from an insecure registry (full registry:port replaced with ${registry})

$ rpm -q podman
podman-1.1.2-1.git0ad9b6b.fc29.x86_64

$ sudo podman pull ${registry}/ubi8
Trying to pull docker://${registry}/ubi8...Failed
(0x1840f00,0xc00041a420)
Error: error pulling image "${registry}/ubi8": Invalid image name "${registry}/ubi8", unknown transport "brew-pulp-docker01.web."

$ sudo podman pull docker://${registry}/ubi8
Trying to pull docker://${registry}/ubi8...Failed
(0x1840f00,0xc00041bba0)

Note in the above error message, the parsing of the registry:port/image specifier seems to break down, as the error message identifies first two portions(brew-pulp-docker01.web) of the full registry name as the transport.

However, if i supplied the --tls=verify=false option, it succeeded:

$ sudo podman pull --tls-verify=false ${registry}/ubi8
Trying to pull docker://${registry}/ubi8...Getting image source signatures
Copying blob 0e403bbe7247 [======================================] 67.6MiB / 67.6MiB
Copying blob 7db10350b227 [======================================] 1.1KiB / 1.1KiB
Copying config af3da4479f [======================================] 4.4KiB / 4.4KiB
Writing manifest to image destination
Storing signatures
af3da4479fde937626dccfad5512acfd064123e2427c911e9824e319958325c4

giuseppe added a commit to giuseppe/libpod that referenced this issue Apr 12, 2019
we were printing something like:

(0x1840f00,0xc00041bba0)

Closes: containers#2710

Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
@giuseppe
Copy link
Member

fixed as part of: #2911

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants