[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 21:11:11 BST 2022
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.
# 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
>
> -rt
>
> On Fri, Aug 19, 2022, 23:39 Michael Musenbrock <michael.musenbrock at gmx.at
> <mailto:michael.musenbrock at gmx.at>> wrote:
>
> Package: podman
> Version: 4.2.0+ds1-3
> Severity: important
>
> 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
>
>
> -- System Information:
> Debian Release: bookworm/sid
> APT prefers unstable
> APT policy: (504, 'unstable'), (503, 'testing'), (502, 'experimental'), (1,
> 'experimental-debug')
> merged-usr: no
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.18.0-4-amd64 (SMP w/16 CPU threads; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages podman depends on:
> ii conmon 2.1.3+ds1-1
> ii crun 1.5+dfsg-1+b1
> ii golang-github-containers-common 0.49.1+ds1-1
> ii libc6 2.34-4
> ii libdevmapper1.02.1 2:1.02.185-1
> ii libgpgme11 1.17.1-4
> ii libseccomp2 2.5.4-1+b1
> ii runc 1.1.3+ds1-7
> ii systemd [systemd-tmpfiles] 251.4-1
>
> Versions of packages podman recommends:
> ii buildah 1.27.0+ds1-5
> ii catatonit 0.1.7-1
> ii dbus-user-session 1.14.0-2
> ii fuse-overlayfs 1.9-1
> ii slirp4netns 1.2.0-1
> ii tini 0.19.0-1
> ii uidmap 1:4.11.1+dfsg1-2
>
> Versions of packages podman suggests:
> ii containers-storage 1.42.0+ds1-1
> ii docker-compose 1.29.2-1
> ii iptables 1.8.8-1
>
> -- no debconf information
>
More information about the Pkg-go-maintainers
mailing list