[Bug 1152721] New: zypper in podman does not install default cni network
http://bugzilla.suse.com/show_bug.cgi?id=1152721 Bug ID: 1152721 Summary: zypper in podman does not install default cni network Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner@suse.de Reporter: kukuk@suse.com QA Contact: qa-bugs@suse.de CC: rbrown@suse.com Found By: --- Blocker: --- zypper in podman and then running a container with podman gives the follow error: Error: error configuring network namespace for container 0b1645ab42470a275c718206f09aaef5d78fc5be5721eb06cee8a13914e9c1cc: Missing CNI default network -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1152721 http://bugzilla.suse.com/show_bug.cgi?id=1152721#c1 Flavio Castelli <fcastelli@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcastelli@suse.com --- Comment #1 from Flavio Castelli <fcastelli@suse.com> --- podman is recommending the podman-cni-config instead of requiring it. As far as I remember the decision was taken because it allows podman to work out of the box on nodes where kubernetes is deployed (it would just reuse the CNI used by k8s, which leads to interesting use cases). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1152721 Shung-Hsi Yu <shung-hsi.yu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |shung-hsi.yu@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1152721 https://bugzilla.suse.com/show_bug.cgi?id=1152721#c2 Ralf Haferkamp <rhafer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #2 from Ralf Haferkamp <rhafer@suse.com> --- (In reply to Flavio Castelli from comment #1)
podman is recommending the podman-cni-config instead of requiring it.
As far as I remember the decision was taken because it allows podman to work out of the box on nodes where kubernetes is deployed (it would just reuse the CNI used by k8s, which leads to interesting use cases).
Right. It seems to have been a deliberate choice to have k8s and podman peacefully co-exist on a machine. -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com