-
Bug
-
Resolution: Unresolved
-
Major
-
rhel-9.4
-
None
-
aardvark-dns-1.13.0-1.el10
-
No
-
Moderate
-
rhel-sst-container-tools
-
3
-
False
-
-
None
-
None
-
Requested
-
None
-
None
What were you trying to do that didn't work?
With podman container added to custom network with network backend "netavark" does not inherit host's resolv.conf
Please provide the package NVR for which bug is seen:
$ rpm -qa | egrep 'podman|netav'
netavark-1.10.3-1.el9.x86_64
podman-4.9.4-6.el9_4.x86_64
How reproducible:
Always
Steps to reproduce
- create new podman nw in rootless/rootful podman
podman network create testdns2 --subnet 10.90.0.0/24 --gateway 10.90.0.1
- create a simple container with above created nw
podman run --rm -d -it --network=testdns2 registry.redhat.io/ubi8
- resolv.conf on host:
$ cat /etc/resolv.conf
Generated by NetworkManager
search rhel94dns.lab.upshift.rdu2.redhat.com
nameserver 10.11.5.160
nameserver 10.2.70.215
4. /etc/resolv.conf on container:
$ podman exec -it 01d59a01a5d1 cat /etc/resolv.conf
search dns.podman
nameserver 10.90.0.1
The behavior is same for both rootful and rootless users however on specifying network backend as "CNI", the resolv.conf is inherited inside the container from the host.
Expected results:
The container should inherit the file /etc/resolv.conf from host.
- clones
-
RHEL-57695 [aardvark-dns-next] DNS non functional when unkown resolv.conf options are present
- Integration
- links to
-
RHBA-2024:140456 aardvark-dns security update