Bug 2055313

Summary: Creating a pod uses bad infra_image registry in podman
Product: Red Hat Enterprise Linux 8 Reporter: Matt Mezynski <mmezynsk>
Component: podmanAssignee: Jindrich Novy <jnovy>
Status: CLOSED CURRENTRELEASE QA Contact: Yuhui Jiang <yujiang>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.5CC: bbaude, cpippin, dornelas, dwalsh, jligon, jnovy, lsm5, mheon, mjtrangoni, pthomas, ranjith.parasuraman, robert.dahlem, snanda, tsweeney, umohnani, vrothber, ypu
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: podman-4.0.3-2.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-09-22 15:38:30 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:

Comment 6 Mario Trangoni 2022-03-08 11:38:08 UTC 
As I am running a VM in china and k8s.gcr.io is blocked there, I faced this issue, and was about to open a dup.

# grep infra_image /usr/share/containers/containers.conf
#infra_image = "k8s.gcr.io/pause:3.4.1"
infra_image = "registry.access.redhat.com/ubi8/pause"

Starting a pod with "podman pod create"
initializing source docker://k8s.gcr.io/pause:3.5: pinging container registry k8s.gcr.io: Get "http://k8s.gcr.io/v2/": dial tcp 108.177.125.82:80: i/o timeout
Error: repository name must have at least one component

Steps to Reproduce:
1. podman pod create
2. podman ps -a --pod

Expected results:
As of previous podman version 3.3.1,
# podman pod create
4cbeba590b7bfa834f2726c63b3a4b6046e01d0bdb1e4e4932371fd793920be9
# podman ps -a --pod
CONTAINER ID  IMAGE                                         COMMAND               CREATED        STATUS          PORTS                                                                         NAMES                                       POD ID        PODNAME
852d4453e640  registry.access.redhat.com/ubi8/pause:latest                        9 seconds ago  Created                                                                                       4cbeba590b7b-infra                          4cbeba590b7b  sharp_williams

Additional info:
As a workaround I had to run, 
dnf downgrade podman containers-common runc for downgrading to 3.3.1
Comment 7 ranjith.parasuraman 2022-04-29 19:47:16 UTC 
Hi,

I am too facing the same problem when creating pod with YAML file.

DEBU[0001] container "db6cf2c7489636bef98fb07238e5a486192c396290c0361fdbad80f8d5ee7cc8" has run directory "/tmp/podman-run-4793/containers/overlay-containers/db6cf2c7489636bef98fb07238e5a486192c396290c0361fdbad80f8d5ee7cc8/userdata"
DEBU[0001] Pulling image  (policy: newer)
Error: repository name must have at least one component


do we have any workaround or fix for this issue. It prevent the POD from getting started.
Comment 9 Tom Sweeney 2022-05-03 22:15:14 UTC 
@asreddy This was not completed until Podman v4.0 and it was not backported in time to make RHEL 8.5 and it is closed now.  Given that, I'm going to set this BZ to POST and will ask @jnovy to take care of any further BZ or packaging needs.  This is fixed in RHEL 8.6 and Podman v4.0.
Comment 21 Red Hat Bugzilla 2023-09-18 04:32:09 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days