spiegel_podman/pkg/domain
Lokesh Mandvekar f6bddc8af2
Remove CNI backend configuration from runtime
Remove runtime configuration options for CNI network backend:

Runtime options:
- Remove WithNetworkBackend() runtime option function
- Function allowed setting network backend programmatically

Flag handling:
- Remove --network-backend flag change detection
- Remove call to WithNetworkBackend() when flag changed
- Remove TODO comment about CNI plugins directory flag

The network backend configuration is now handled entirely by the
vendored common/libnetwork code, which will default to Netavark.
There is no longer any way to configure CNI as the network backend
through Podman's runtime initialization.

Note: libpod/info.go keeps existing NetworkBackend reporting logic
which will automatically report "netavark" as the only backend since
configuration defaults to netavark and cannot be changed to CNI.

Signed-off-by: Lokesh Mandvekar <lsm5@redhat.com>
2026-01-27 16:32:38 +05:30
..
entities Merge pull request #26445 from aaron-ang/update-ulimit 2026-01-16 08:38:00 -05:00
filters Fix unless-stopped restart policy to match Docker behavior 2025-12-02 15:40:46 +01:00
infra Remove CNI backend configuration from runtime 2026-01-27 16:32:38 +05:30
utils enable gofumpt formatter 2025-11-11 12:32:46 +01:00