I've noticed that we don't deploy the default sample configuration for Podman (https://github.com/containers/podman/blob/main/cni/87-podman-bridge.conflist), but rather we rely on Podman creating the default network for us. FMU, this is a fail-safe if Podman cannot find any network; and I don't know if it's intended to be used this way. Most other distros seem to deploy the file `87-podman-bridge.conflist` in `/etc/cni/net.d` to control the default Podman network. It's also documented this way on the official documentation (https://podman.io/getting-started/network.html). Beyond all this, not having the file prevents you from making any modifications to the default network, it seems. This can be problematic if you intend to use one of the CNI plugins with the default `podman` network. Therefore, I would propose deploying the file; unless, of course, there's some reason we're not deploying the file, that I don't know of. Reproducible: Always
FWIW if this is deemed acceptable, I don't mind submitting a PR for this.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fc2204a2325f3feaff80d6195c307135de462811 commit fc2204a2325f3feaff80d6195c307135de462811 Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2023-05-09 05:06:52 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2023-05-09 05:16:23 +0000 app-containers/podman: add 4.5.0 Closes: https://bugs.gentoo.org/847025 Closes: https://bugs.gentoo.org/895858 Closes: https://bugs.gentoo.org/903285 Closes: https://bugs.gentoo.org/904399 Signed-off-by: Zac Medico <zmedico@gentoo.org> app-containers/podman/Manifest | 1 + app-containers/podman/podman-4.5.0.ebuild | 172 ++++++++++++++++++++++++++++++ 2 files changed, 173 insertions(+)
