Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
There is a docker login registry compatiliby issue. Please see:
https://github.com/containers/podman/issues/17571 for details.
This is already fixed upstream, creating BZs to get it into RHEL 8.8/9.2 ZeroDay.
For RHEL 8.8 and 9.2, this Fix: https://github.com/containers/podman/pull/17581 needs to be backported into the Podman v4.4.1 release branch, and c/common needs to be bumped up to v0.51.2 within the same branch.
This bug has been verified on podman-4.4.1-13.module+el8.9.0+18566+0239040b.
[test@kvm-02-guest05 ~]$ cat /etc/redhat-release
Red Hat Enterprise Linux release 8.9 Beta (Ootpa)
[test@kvm-02-guest05 ~]$ rpm -q podman runc systemd kernel
podman-4.4.1-13.module+el8.9.0+18566+0239040b.x86_64
runc-1.1.5-1.module+el8.9.0+18566+0239040b.x86_64
systemd-239-74.el8_8.x86_64
kernel-4.18.0-484.el8.x86_64
[test@kvm-02-guest05 ~]$ id
uid=1000(test) gid=1000(test) groups=1000(test) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
[test@kvm-02-guest05 ~]$ podman system service -t 0 &
[1] 122681
[test@kvm-02-guest05 ~]$ podman run --privileged -it --rm -v $XDG_RUNTIME_DIR/podman/podman.sock:/var/run/docker.sock docker sh
/ # docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
docker latest e072c2e5e550 6 days ago 319MB
/ # docker login -u foo -p bar
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Error response from daemon: login attempt to https://index.docker.io/v1/ failed with status: 401 Unauthorized
NOTE: I can login successfully w/ real username and password.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: container-tools:rhel8 security and bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2023:6939