diff options
| author | Bruce Ashfield <bruce.ashfield@gmail.com> | 2026-06-04 03:16:13 +0000 |
|---|---|---|
| committer | Bruce Ashfield <bruce.ashfield@gmail.com> | 2026-06-04 03:31:56 +0000 |
| commit | 0ab5d81a5f5ccd985ca2e4819bb515268a04f2e1 (patch) | |
| tree | f54c797918337daab19829e7f4ee76bb3c134f00 /recipes-networking | |
| parent | b8d9e23c511e815ad5a9cf0d1d58a1ef074f1f32 (diff) | |
| download | meta-virtualization-0ab5d81a5f5ccd985ca2e4819bb515268a04f2e1.tar.gz | |
podman: switch from CNI to netavark as sole network backend
Podman's vendored containers/common library removed CNI support
entirely in commit 8d1f636e40 (March 2026). The NetworkBackend()
function now unconditionally rejects any backend other than netavark,
making network_backend = "cni" in containers.conf a runtime error.
The vpdmn rootfs originally used CNI because netavark's dependency
chain (nmap -> libpcap -> bluez5 -> cairo) was too heavy for the
vruntime BBMASK environment. That dependency chain no longer exists
— netavark v1.16.0+ uses a built-in Rust connection tester and has
no heavyweight runtime dependencies.
Recipe changes:
- Clear BUILDTAGS_EXTRA default (was CNI build tag, now a no-op)
- Set VIRTUAL-RUNTIME_container_networking and _container_dns with
strong assignments so podman always RDEPENDS on netavark and
aardvark-dns regardless of distro config
- Remove ${sysconfdir}/cni from FILES
vpdmn rootfs changes:
- Replace cni with netavark + aardvark-dns in IMAGE_INSTALL
- Update containers.conf network_backend from cni to netavark
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Diffstat (limited to 'recipes-networking')
0 files changed, 0 insertions, 0 deletions