diff options
| author | Bruce Ashfield <bruce.ashfield@gmail.com> | 2026-04-29 16:22:48 +0000 |
|---|---|---|
| committer | Bruce Ashfield <bruce.ashfield@gmail.com> | 2026-04-29 16:57:14 +0000 |
| commit | 3106e77f8146a8e48c1948d00354218e2b19b819 (patch) | |
| tree | 627a0cae2642e31e2cceddbc6e58a562dae13cb9 /recipes-devtools/python/python-docopt.inc | |
| parent | 751b99dc32d7d439031df42730a8ed65e82b3e95 (diff) | |
| download | meta-virtualization-3106e77f8146a8e48c1948d00354218e2b19b819.tar.gz | |
podman: fix CNI build tag for non-netavark networking configurations
BUILDTAGS_EXTRA was gated on VIRTUAL-RUNTIME_container_networking == "cni",
which excluded the cni build tag in vruntime builds where that variable is
intentionally blank (vpdmn-rootfs-image installs cni packages directly).
This caused podman to be compiled with netavark-only support, failing at
runtime with "cni support is not enabled in this build" when containers.conf
sets network_backend = "cni".
Include the cni build tag unless the distro explicitly selects netavark.
This respects the podman profile's upstream preference for netavark-only
while ensuring all other configurations (containerd, default, docker, k3s,
vruntime) retain CNI support.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Diffstat (limited to 'recipes-devtools/python/python-docopt.inc')
0 files changed, 0 insertions, 0 deletions