[pkg-go] Bug#1017766: podman: Failed to activate DNS. Missing dependency on golang-github-containernetworking-plugin-dnsname

Michael Musenbrock michael.musenbrock at gmx.at
Sat Aug 20 22:47:45 BST 2022

On 20.08.22 22:11, Michael Musenbrock wrote:
> On 20.08.22 20:01, Reinhard Tartler wrote:
>>  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?
> netavarak was already installed, but aardvark-dns not. I uninstalled the
> golang-github-containernetworking-plugin-dnsname and installed aardvark-dns.

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

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.

> # 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.

More information about the Pkg-go-maintainers mailing list