linux/meta-virtualization.git/conf/distro/include/meta-virt-container.inc, branch master-next

container-registry: use FEATURE_PACKAGES for IMAGE_FEATURES validation

2026-03-12T19:18:50+00:00

Move FEATURE_PACKAGES_container-registry from container-image-host.bb to meta-virt-container.inc so it is available to all image recipes. image.bbclass check_image_features() auto-discovers FEATURE_PACKAGES_* variables as valid image features (line 72), so defining the variable globally is sufficient — no IMAGE_FEATURES[validitems] needed. This avoids the signature pollution that IMAGE_FEATURES[validitems] causes when set globally, while allowing container-registry to be used as an IMAGE_FEATURES value in any image recipe. Signed-off-by: Bruce Ashfield

conf: meta-virt-container.inc comment out values as reference

2024-11-15T19:50:00+00:00

This .inc file is no longer the active one by default, so we will use it a reference for the possible values. To make that more obvious, we comment out the current values. Signed-off-by: Bruce Ashfield

meta-virt-container.inc: Install shadow in read-only rootfs

2024-10-03T01:28:52+00:00

Podman requires /etc/sub[g]uid for rootless mode but the file is being deleted if shadow is in ROOTFS_RO_UNNEEDED (even if different package like the podman itself provides it) and rpm backend is used. Signed-off-by: Pavel Zhukov Signed-off-by: Bruce Ashfield

conf: introduce container configuration values

2023-03-08T22:08:02+00:00

From the configuration file itself: These variables represent groupings of functionality in the CNCF landscape. In particular, they are areas where there is a choice between more than one implementation or an area where abstraction is beneficial. The contents of the variables are are runtime components that recipes may use for RDEPENDS. Build dependencies are not typically flexible, so do not currently have DEPENDS equivalents for the components (i.e. DEPENDS on runc versus crun). Distro features such as kubernetes or other container stacks can be used to set different defaults for these variables. Note: these are "global" values, since they represent choices. If more than of a grouping is required on target, then the variable can be appended or set to multiple values. That being said, Recipes should generally agree on the values, hence the global namespace. Recipe specific choices can still be done, but they risk conflicting on target or causing runtime issues / errors. ## CNCF "components" # engines: docker-ce/docker-moby, virtual-containerd, cri-o, podman VIRTUAL-RUNTIME_container_engine ??= "podman" # runtime: runc, crun, runv, runx VIRTUAL-RUNTIME_container_runtime ??= "virtual-runc" # networking: cni, netavark VIRTUAL-RUNTIME_container_networking ??= "cni" # dns: cni, aardvark-dns VIRTUAL-RUNTIME_container_dns ??= "cni" # orchestration: k8s, k3s VIRTUAL-RUNTIME_container_orchestration ??= "k3s" ## Kubernetes terminology "components" VIRTUAL-RUNTIME_cri ??= "containerd" VIRTUAL-RUNTIME_cni ??= "cni" Signed-off-by: Bruce Ashfield