`docker login` with docker.io creds "successfully" logs-into `registry.fedoraproject.org` then fails to push to `registry-1.docker.io` #22400

rhatdan · 2024-04-16T21:00:44Z

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 for registry.fedoraproject.org (not what I expected), but when I try to push it tries to push to registry-1.docker.io (is what I expected).

Steps to reproduce the issue

Install podman-docker
Follow docker.io's instructions to login
a. Create access token
b. run docker login -u $USER
c. enter token

Describe the results you received

$ podman login -u $USER
Password:
Login Succeeded!
$ cat /run/user/1000/containers/auth.json
{
    "auths": {
	    "registry.fedoraproject.org": {
		    "auth": "cGF0cmljazpkY2tyX3BhdF84X2xvbHRoaXNhaW50cmVhbAo="
	    }
    }
}⏎
$ docker push $USER/$IMAGE
[...]
Error: writing blob: initiating layer upload to /v2/$USER/$IMAGE/blobs/uploads/ in registry-1.docker.io: requested access to the resource is denied

Describe the results you expected

$ docker login -u $USER
Password: 
Login Succeeded!
$ cat /run/user/1000/containers/auth.json
{
    "auths": {
	    "registry-1.docker.io": {
		    "auth": "cGF0cmljazpkY2tyX3BhdF84X2xvbHRoaXNhaW50cmVhbAo="
	    }
    }
}⏎
$ docker push $USER/$IMAGE
Writing manifest to image destination

^ exit success

or

Failure for the login command

podman info output

host:
  arch: amd64
  buildahVersion: 1.33.7
  cgroupControllers:
  - cpu
  - io
  - memory
  - pids
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.1.10-1.fc39.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.10, commit: '
  cpuUtilization:
    idlePercent: 94.97
    systemPercent: 1.49
    userPercent: 3.54
  cpus: 20
  databaseBackend: sqlite
  distribution:
    distribution: fedora
    variant: workstation
    version: "39"
  eventLogger: journald
  freeLocks: 2039
  hostname: brick
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 524288
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 524288
      size: 65536
  kernel: 6.7.11-200.fc39.x86_64
  linkmode: dynamic
  logDriver: journald
  memFree: 40281542656
  memTotal: 67076845568
  networkBackend: netavark
  networkBackendInfo:
    backend: netavark
    dns:
      package: aardvark-dns-1.10.0-1.fc39.x86_64
      path: /usr/libexec/podman/aardvark-dns
      version: aardvark-dns 1.10.0
    package: netavark-1.10.3-1.fc39.x86_64
    path: /usr/libexec/podman/netavark
    version: netavark 1.10.3
  ociRuntime:
    name: crun
    package: crun-1.14.4-1.fc39.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 1.14.4
      commit: a220ca661ce078f2c37b38c92e66cf66c012d9c1
      rundir: /run/user/1000/crun
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJL
  os: linux
  pasta:
    executable: /usr/bin/pasta
    package: passt-0^20240220.g1e6f92b-1.fc39.x86_64
    version: |
      pasta 0^20240220.g1e6f92b-1.fc39.x86_64
      Copyright Red Hat
      GNU General Public License, version 2 or later
        <https://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
      This is free software: you are free to change and redistribute it.
      There is NO WARRANTY, to the extent permitted by law.
  remoteSocket:
    exists: true
    path: /run/user/1000/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.2.2-1.fc39.x86_64
    version: |-
      slirp4netns version 1.2.2
      commit: 0ee2d87523e906518d34a6b423271e4826f71faf
      libslirp: 4.7.0
      SLIRP_CONFIG_VERSION_MAX: 4
      libseccomp: 2.5.3
  swapFree: 8589930496
  swapTotal: 8589930496
  uptime: 25h 7m 53.00s (Approximately 1.04 days)
  variant: ""
plugins:
  authorization: null
  log:
  - k8s-file
  - none
  - passthrough
  - journald
  network:
  - bridge
  - macvlan
  - ipvlan
  volume:
  - local
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - docker.io
  - quay.io
store:
  configFile: /home/$USER/.config/containers/storage.conf
  containerStore:
    number: 3
    paused: 0
    running: 2
    stopped: 1
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /home/$USER/.local/share/containers/storage
  graphRootAllocated: 4095101370368
  graphRootUsed: 37661007872
  graphStatus:
    Backing Filesystem: btrfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Supports shifting: "false"
    Supports volatile: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 26
  runRoot: /run/user/1000/containers
  transientStore: false
  volumePath: /home/$USER/.local/share/containers/storage/volumes
version:
  APIVersion: 4.9.4
  Built: 1711445992
  BuiltTime: Tue Mar 26 04:39:52 2024
  GitCommit: ""
  GoVersion: go1.21.8
  Os: linux
  OsArch: linux/amd64
  Version: 4.9.4

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 run docker login -u $USER registry-1.docker.io instead.

The text was updated successfully, but these errors were encountered:

rhatdan · 2024-04-16T21:05:15Z

I guess the login successfull command should say

Login Succeeded registry.fedoraproject.org!

Or potentially better, if Podman and Buildah could figure it out, would be to return an error and tell the user to specify the registry. This is probably the more secure thing to do, since your credentials were sent to registry.fedoraproject.org.

If podman/buildah know that there are more then one registry, and the user does not specify one, it should error and tell the user to specify a registry.

rhatdan · 2024-04-16T21:05:48Z

Just need someone to step up to open a PR.

github-actions · 2024-05-17T00:07:11Z

A friendly reminder that this issue had no activity for 30 days.

tthvo · 2024-05-18T01:50:36Z

Mind if I have a look? I am new here so just need to get familiar with the codebase :))

rhatdan · 2024-05-18T02:37:25Z

You got it.

tthvo · 2024-05-22T00:11:20Z

Or potentially better, if Podman and Buildah could figure it out, would be to return an error and tell the user to specify the registry. This is probably the more secure thing to do, since your credentials were sent to registry.fedoraproject.org.
If podman/buildah know that there are more then one registry, and the user does not specify one, it should error and tell the user to specify a registry.

@rhatdan hi, I have a question as I am walking through this. This does mean that podman login/logout would not be compatible with docker, right? Essentially, reverting #5233?

Login Succeeded registry.fedoraproject.org!

Otherwise, this makes sense to me! Seems like its out of scope of podman and must be done in https://github.com/containers/common.

What are your thoughts?

danishprakash · 2024-05-24T07:34:18Z

Login Succeeded registry.fedoraproject.org!

Otherwise, this makes sense to me!

I'd suggest reverting #5233 since logging in unintentionally to a different registry doesn't look good from a security point of view.

If reverting is not ideal, then we can let the user confirm their choice while displaying the registry podman would end up logging in to, allowing the user to choose not to login to a different registry and modifying the registries.conf as desired or even pass the registry as a flag.

tthvo · 2024-05-24T08:03:53Z

Sounds reasonable to me on the security standpoint! I suppose anyone would not want their credentials sent elsewhere unintended, for example, a tampered registries.conf.

If reverting is not ideal, then we can let the user confirm their choice while displaying the registry podman would end up logging in to, allowing the user to choose not to login to a different registry and modifying the registries.conf as desired or even pass the registry as a flag.

This is a good idea here. Though, it can be a bit tough for non-interactive login that would just want to skip confirmation. Something like podman login -y <registry> might be ok, but it does sound odd and maybe there are better ways.

tthvo · 2024-06-06T03:16:53Z

To keep it simple for now unless we decide otherwise later, I will have a look to output the registry that is being logged in.

arsenalzp · 2024-11-24T16:25:02Z

Hello,
Does anybody work on this issue?
If no, please assign it to me. I would also know are there any deadlines for solving this issue?

tthvo · 2024-11-26T05:48:51Z

Hello,
Does anybody work on this issue?
If no, please assign it to me. I would also know are there any deadlines for solving this issue?

Hey @arsenalzp , I have yet to hear back on which direction to go in this issue, so there has yet to be any progress. Though, not sure if I have the time in the next couple months, so feel free to work on it :D

arsenalzp · 2024-11-27T12:15:39Z

Please assign it to me.

lslavkov · 2024-12-12T14:35:29Z

Greetings! I want to take the mantle to fix this but seems that @arsenalzp is next in line for fixing the issue.

lslavkov · 2024-12-13T13:54:42Z

@rhatdan

If podman/buildah know that there are more then one registry, and the user does not specify one, it should error and tell the user to specify a registry.

So If I understand correctly it needs to ask specific registry if there is already one in the auth.json to avoid collisions, right?

lslavkov · 2024-12-13T19:23:52Z

/assign

rhatdan · 2024-12-13T19:28:00Z

Awesome thanks @lslavkov

lslavkov · 2024-12-14T20:02:57Z

@danishprakash

I'd suggest reverting #5233 since logging in unintentionally to a different registry doesn't look good from a security point of view.

I don't think that is really ideal situation to revert the code. Based on commits I have checked that is no longer possible to return on that point. Would need to code the stuff for that.

If reverting is not ideal, then we can let the user confirm their choice while displaying the registry podman would end up logging in to, allowing the user to choose not to login to a different registry and modifying the registries.conf as desired or even pass the registry as a flag.

Would be better to fail command with context of like you have not declared a registry to login?

rhatdan · 2024-12-16T13:49:49Z

How about if you have more then one registry then we force users to enter the specific registry. Then if they only have one listed, it just works.

lslavkov · 2024-12-16T14:35:58Z

How about if you have more then one registry then we force users to enter the specific registry. Then if they only have one listed, it just works.

~~Registry in auth.json file I assume?~~

@rhatdan

Actually it is better to target directly the registry from registry.conf. Your thoughts?

rhatdan · 2024-12-18T16:34:10Z

That is what I was talking about.

If you have one unqualified registry listed in registry.conf say quay.io, then
podman login

Should work as well as
podman login REGISTRY

If we have more then one unqualified registry in registries.conf, then
podman login

SHould throw an error saying please pick a registry.

rhatdan added the kind/bug Categorizes issue or PR as related to a bug. label Apr 16, 2024

rhatdan added the Good First Issue This issue would be a good issue for a first time contributor to undertake. label Apr 16, 2024

github-actions bot added the stale-issue label May 17, 2024

rhatdan assigned tthvo May 18, 2024

rhatdan removed the stale-issue label May 18, 2024

openshift-ci bot assigned lslavkov Dec 13, 2024

lslavkov linked a pull request Dec 21, 2024 that will close this issue

Checking for multiple registries when login/logout #24888

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

`docker login` with docker.io creds "successfully" logs-into `registry.fedoraproject.org` then fails to push to `registry-1.docker.io` #22400

`docker login` with docker.io creds "successfully" logs-into `registry.fedoraproject.org` then fails to push to `registry-1.docker.io` #22400

rhatdan commented Apr 16, 2024

Issue Description

Steps to reproduce the issue

Describe the results you received

Describe the results you expected

podman info output

Podman in a container

Privileged Or Rootless

Upstream Latest Release

Additional environment details

Additional information

Workaround

rhatdan commented Apr 16, 2024

rhatdan commented Apr 16, 2024

github-actions bot commented May 17, 2024

tthvo commented May 18, 2024

rhatdan commented May 18, 2024

tthvo commented May 22, 2024 •

edited

Loading

danishprakash commented May 24, 2024 •

edited

Loading

tthvo commented May 24, 2024 •

edited

Loading

tthvo commented Jun 6, 2024

arsenalzp commented Nov 24, 2024 •

edited

Loading

tthvo commented Nov 26, 2024

arsenalzp commented Nov 27, 2024

lslavkov commented Dec 12, 2024

lslavkov commented Dec 13, 2024

lslavkov commented Dec 13, 2024

rhatdan commented Dec 13, 2024

lslavkov commented Dec 14, 2024

rhatdan commented Dec 16, 2024

lslavkov commented Dec 16, 2024 •

edited

Loading

rhatdan commented Dec 18, 2024

docker login with docker.io creds "successfully" logs-into registry.fedoraproject.org then fails to push to registry-1.docker.io #22400

docker login with docker.io creds "successfully" logs-into registry.fedoraproject.org then fails to push to registry-1.docker.io #22400

Comments

rhatdan commented Apr 16, 2024

Discussed in #22394

Issue Description

Steps to reproduce the issue

Describe the results you received

Describe the results you expected

podman info output

Podman in a container

Privileged Or Rootless

Upstream Latest Release

Additional environment details

Additional information

Workaround

rhatdan commented Apr 16, 2024

rhatdan commented Apr 16, 2024

github-actions bot commented May 17, 2024

tthvo commented May 18, 2024

rhatdan commented May 18, 2024

tthvo commented May 22, 2024 • edited Loading

danishprakash commented May 24, 2024 • edited Loading

tthvo commented May 24, 2024 • edited Loading

tthvo commented Jun 6, 2024

arsenalzp commented Nov 24, 2024 • edited Loading

tthvo commented Nov 26, 2024

arsenalzp commented Nov 27, 2024

lslavkov commented Dec 12, 2024

lslavkov commented Dec 13, 2024

lslavkov commented Dec 13, 2024

rhatdan commented Dec 13, 2024

lslavkov commented Dec 14, 2024

rhatdan commented Dec 16, 2024

lslavkov commented Dec 16, 2024 • edited Loading

rhatdan commented Dec 18, 2024

`docker login` with docker.io creds "successfully" logs-into `registry.fedoraproject.org` then fails to push to `registry-1.docker.io` #22400

`docker login` with docker.io creds "successfully" logs-into `registry.fedoraproject.org` then fails to push to `registry-1.docker.io` #22400

tthvo commented May 22, 2024 •

edited

Loading

danishprakash commented May 24, 2024 •

edited

Loading

tthvo commented May 24, 2024 •

edited

Loading

arsenalzp commented Nov 24, 2024 •

edited

Loading

lslavkov commented Dec 16, 2024 •

edited

Loading