-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
rhel-9.3.0
-
None
-
None
-
Moderate
-
1
-
sst_container_tools
-
0
-
False
-
-
None
-
Red Hat Enterprise Linux
-
RUN 255
-
None
-
None
-
None
Issue : rootless podman container can't resolve https://cdn-ubi.redhat.com when using a custom network
Observations :
- Issue is with RHEL 9.3, podman-4.6.1 and with ubi9 image in customer's environment
- Could not reproduce in our test environment
- works expected with ubi8 image on RHEL 9.3, podman-4.6.1
- worked expected with podman to 4.4.1
Reproducer Steps :
$ podman network create test-network
test-network
$ podman network ls
NETWORK ID NAME DRIVER
2f259bab93aa podman bridge
dbeedca84a3f test-network bridge
$ podman run -it --rm --network=test-network registry.access.redhat.com/ubi9:9.3-1361.1699548029 /bin/bash
[root@8e7e98687352 /]# dnf update
Updating Subscription Management repositories.
Unable to read consumer identity
subscription-manager is operating in container mode.
This system is not registered with an entitlement server. You can use subscription-manager to register.
Red Hat Enterprise Linux 9 for x86_64 - BaseOS (RPMs) 9.3 MB/s | 16 MB 00:01
Red Hat Enterprise Linux 9 for x86_64 - AppStream (RPMs) 12 MB/s | 28 MB 00:02
Red Hat Universal Base Image 9 (RPMs) - BaseOS 23 B/s | 124 B 00:05
Errors during downloading metadata for repository 'ubi-9-baseos-rpms':
- Curl error (6): Couldn't resolve host name for https://cdn-ubi.redhat.com/content/public/ubi/dist/ubi9/9/x86_64/baseos/os/repodata/c3c3d68ba67ec5aa22dec2c1ce7049601abcfa523f3d980bef036dfd84f4accf-primary.xml.gz [Could not resolve host: cdn-ubi.redhat.com]
- Curl error (6): Couldn't resolve host name for https://cdn-ubi.redhat.com/content/public/ubi/dist/ubi9/9/x86_64/baseos/os/repodata/3e60d5f033c77743f3a9fe77a193e38cfd91156a65d709159720a6e6ccd88052-filelists.xml.gz [Could not resolve host: cdn-ubi.redhat.com]
- duplicates
-
RHEL-17270 [netavark-1.12.0] aardvark-dns needs TCP support
- Release Pending
- links to