#1017766 podman: Failed to activate DNS. Missing dependency on golang-github-containernetworking-plugin-dnsname

Package:
podman
Source:
podman
Description:
tool to manage containers and pods
Submitter:
Michael Musenbrock
Date:
2023-04-10 21:48:03 UTC
Severity:
normal
#1017766#5
Date:
2022-08-19 21:35:32 UTC
From:
To:
Hi,

thanks for bringing up-to-date podman packages to Debian. This is really nice to have those current version available.

With the latest version of the podman packages (4.2.0+ds1-3) dns resolution fails for podman networks.

This could simply be resolved by installing 'golang-github-containernetworking-plugin-dnsname'. I think this should be installed automatically via dependencies.

hth, keep up the nice work
regards Michael
#1017766#10
Date:
2022-08-20 18:01:25 UTC
From:
To:
From the list of packages in your big report i see that the packages
netavark and aardvark-dns are absent. Does installing them work for your
without the golang-github-containernetworking-plugin-dnsname package?


One of the main major changes in podman 4 is the rust based networking
stack. It should be installed by default for new installations. Did this
not happen or is this an upgrade situation?
#1017766#15
Date:
2022-08-20 20:11:11 UTC
From:
To:
netavarak was already installed, but aardvark-dns not. I uninstalled the
golang-github-containernetworking-plugin-dnsname and installed aardvark-dns.


# dpkg -l | grep -e aardvark-dns -e netavark -e
golang-github-containernetworking-plugin-dnsname
ii  aardvark-dns                                     1.0.3-1+b1
ii  netavark                                         1.0.3-3

Afterwards I got the DNS issue again.

The reason why I tried the golang package in the first place, was that I saw the following
message in a 'podman network ls'
 > WARN[0000] Error validating CNI config file
/home/michael/.config/cni/net.d/caba086a-7c97-46ba-87c2-f3cec00c71c2.conflist: [failed to
find plugin "dnsname" in path [/usr/local/libexec/cni /usr/libexec/cni /usr/local/lib/cni
/usr/lib/cni /opt/cni/bin]]

 >
 > One of the main major changes in podman 4 is the rust based networking stack. It should be
 > installed by default for new installations. Did this not happen or is this an upgrade
 > situation?

 From the installation history: I installed 4.1.1+ds1-2 first on this machine, and then did
the upgrade to 4.2.

br m
#1017766#20
Date:
2022-08-20 21:47:45 UTC
From:
To:
I retried and checked 'podman info --format {{.Host.NetworkBackend}}', which still
reported 'cni'.

So I changed the containers.conf and specified netavark as network_backend in the
Network-section.

Afterwards 'podman info --format {{.Host.NetworkBackend}}' reported 'netavark'.

Now a dns-server is active in the network, but the other pods attached to the network
still can't be resolved. But this may be just some config issue. I will check.
#1017766#25
Date:
2022-09-10 17:47:00 UTC
From:
To:
Hi Michael,
just checking in, did you had a chance to check whether this is a config
issue?

In any case, any chance you could describe your test setup? I'm still
looking
for a minimal test case that would be able to demonstrate the issue, and
thought
you might be able to help?

Best,
-rt
#1017766#30
Date:
2023-04-10 21:45:13 UTC
From:
To:
Hi Michael,
Unfortunately, I haven't heard back from you in many months. I'm therefore
going to close
this bug report for now. If you have any additional information or
suggestions how
I could reproduce this issue, please don't hesitate to respond to this
email and make
sure to copy 1017766@bugs.debian.org in your response.

Thanks!