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:
If using host:port, IOW when specifying a port explicitly, "podman images" is confused, putting the port together with the path and tag.

Version-Release number of selected component (if applicable):
podman-docker-2.0.0-0.9.rc7.module+el8.3.0+7084+c16098dd

How reproducible:
Always. I originally noticed this while using RHUI, where containers are served on port 5000, but this is reproducible with common registries as long as you enter the (default) port manually.

Steps to Reproduce:
1. podman pull registry.access.redhat.com:443/ubi8
2. podman images

Actual results:
REPOSITORY                               TAG              IMAGE ID      CREATED      SIZE
registry.access.redhat.com               443/ubi8:latest  a523835cfc89  10 days ago  212 MB

Expected results:
This was OK in RHEL 8.2:
REPOSITORY                            TAG      IMAGE ID       CREATED       SIZE
registry.access.redhat.com:443/ubi8   latest   a523835cfc89   10 days ago   212 MB

Radek, could you include the output from `podman --version' please?

Parker, please take a look at this.  First upstream, and then in the version that Radek replies with.

Sure, Tom:

podman version 2.0.0-rc7

Hi Radek,

I can verify that this bug indeed exists in your version.
This bug has been fixed in the upstream, https://github.com/containers/podman/pull/6934.
It will be included in a future RHEL release.

This landed in Podman 2.0.3, which is targeted for 8.3.0 release.

Setting this BZ to Post as the fix is upstream and Jindrich will need to touch up some packaging details next week.

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, bug fix, and enhancement 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-2020:4694