Bug 1853230

Summary:	The output from "podman images" is malformed if a repository contains a port
Product:	Red Hat Enterprise Linux 8	Reporter:	Radek Bíba <rbiba>
Component:	podman	Assignee:	Jindrich Novy <jnovy>
Status:	CLOSED ERRATA	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	medium	Docs Contact:	Gabriela Nečasová <gnecasov>
Priority:	unspecified
Version:	8.3	CC:	bbaude, dwalsh, jligon, jnovy, lmanasko, lmiksik, lsm5, mheon, tsweeney, vrothber, ypu, yujiang
Target Milestone:	rc	Keywords:	Regression
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	podman 2.0.2-2 and newer	Doc Type:	Bug Fix
Doc Text:	.`podman images` output is not malformed if a repository contains a port Previously, pulling container images using `podman pull <host:port>` command with explicitly specified port and subsequent listing images using `podman images` command results in incorrect output and the port displayed together with the path and tag. With this update, the output of the `podman images` command is correctly displayed.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-04 03:05:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1840500

Description Radek Bíba 2020-07-02 08:25:05 UTC

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

Comment 1 Tom Sweeney 2020-07-02 17:41:50 UTC

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

Comment 2 Tom Sweeney 2020-07-02 17:47:22 UTC

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

Comment 3 Radek Bíba 2020-07-02 21:42:48 UTC

Sure, Tom:

podman version 2.0.0-rc7

Comment 4 Parker Van Roy 2020-07-20 16:41:25 UTC

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.

Comment 11 Matthew Heon 2020-07-24 12:59:06 UTC

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

Comment 13 Tom Sweeney 2020-07-24 18:26:13 UTC

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

Comment 23 errata-xmlrpc 2020-11-04 03:05:17 UTC

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