docker login
with docker.io creds "successfully" logs-into registry.fedoraproject.org
then fails to push to registry-1.docker.io
#22400
Labels
Good First Issue
This issue would be a good issue for a first time contributor to undertake.
kind/bug
Categorizes issue or PR as related to a bug.
Discussed in #22394
Originally posted by azdle April 16, 2024
Issue Description
First off, I'm not sure if this is a podman issue or a fedora package issue, but I figured this might be helpful here since there are a lot of closed, but unresolved, issues here that seem like they could be caused by this. Also, this is on 4.9.4, I haven't tried v5.
Doing a fresh setup with
podman-docker
installed on fedora and following docker.io's instructions for logging in and pushing my first image, I'm told my "Login Succeeded!", but when I try to push I get a "resource denied" error.It seems running
docker login -u $USER
stores the access token as a token forregistry.fedoraproject.org
(not what I expected), but when I try to push it tries to push toregistry-1.docker.io
(is what I expected).Steps to reproduce the issue
a. Create access token
b. run
docker login -u $USER
c. enter token
Describe the results you received
Describe the results you expected
^ exit success
or
Failure for the login command
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
No response
Additional information
Workaround
For anyone else having this issue, either edit your
auth.json
file to say "registry-1.docker.io" or just rundocker login -u $USER registry-1.docker.io
instead.The text was updated successfully, but these errors were encountered: