[Bug 1206950] (podman) dnsname plugin isn't available so containers can't resolve each other
https://bugzilla.suse.com/show_bug.cgi?id=1206950 https://bugzilla.suse.com/show_bug.cgi?id=1206950#c4 Alexandre Vicenzi <alexandre.vicenzi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|containers-bugowner@suse.de |alexandre.vicenzi@suse.com Status|NEW |RESOLVED Resolution|--- |INVALID CC| |alexandre.vicenzi@suse.com, | |containers-bugowner@suse.de --- Comment #4 from Alexandre Vicenzi <alexandre.vicenzi@suse.com> --- I'm not able to reproduce this using a compose file that has `depends_on` and `links` to another container. cni-plugin-dnsname is not installed on my machine. From the official README [1]. podman dnsname plugin: It is usually found in the podman-plugins or podman-dnsname distro packages, those packages are not pulled by default and you need to install them. This allows containers to be able to resolve each other if they are on the same CNI network. This is not necessary when podman is using netavark as a network backend. Tumbleweed uses netavark, you can see it with `podman info`: networkBackendInfo: backend: netavark This is not an issue, if netavark is not used, you need to manually install an additional package. Something to consider, as of 2023, the dnsname plugin is no longer actively maintained, it reached EOL. [1]: https://github.com/containers/podman-compose?tab=readme-ov-file#podman-compo... -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com