-
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
podman pull from docker.io - unauthorized #7780
Comments
Does it work if you pull by fully-qualified name |
no, it doesn't. |
Did you login as root and pulled as root? |
You must podman login first to get this image. |
I'll re-open as the issue states that it's failing despite the login. |
Does it succeed on Docker then, and Not on Podman? |
Can you try with a newer version of Podman? |
try reading again 😃 |
see output of the command - everything is done as root :) |
I have also tried with podman 2.1 from Solus distro, same result |
Can you try pulling another image? For instance, a private one form your own namespace? Maybe you don't have permission to access pi-hole? |
Could you attempt to pull the image with Skopeo and or buildah to see if they act differently? |
This is the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=1867495 that has been fixed. So close this. |
Original commentHello. The bugzilla link shows that the problem is fixed in podman v1.6.4, but I still encountered a similar problem in podman v3.0.1
Edit: It's a typo... The correct image is |
I get the image by |
👍🏼 |
/kind bug
After a successful login with
podman login docker.io
I cannot pull anything because authorization is required ...
Steps to reproduce the issue:
podman login docker.io
podman pull pi-hole/pi-hole
Result
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
No
The text was updated successfully, but these errors were encountered: