vcontainer: fix runc/crun conflict in multiconfig builds

The vruntime distro is used for multiconfig builds of both vdkr
(Docker/runc) and vpdmn (Podman/crun) images. When CONTAINER_PROFILE
or VIRTUAL-RUNTIME_container_runtime is set, containerd and podman
pull their preferred runtime via RDEPENDS, causing package conflicts.

Fix by having vruntime distro NOT participate in CONTAINER_PROFILE:
- Set VIRTUAL-RUNTIME_container_runtime="" to prevent automatic
  runtime selection
- Explicitly install runc in vdkr-rootfs-image.bb
- Explicitly install crun in vpdmn-rootfs-image.bb

This allows both images to be built in the same multiconfig without
conflicts, while standard container-host images continue to use
CONTAINER_PROFILE normally.

Also add kernel-modules to vdkr-rootfs-image for overlay filesystem
support.

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>

1 files changed, 17 insertions, 2 deletions

diff --git a/conf/distro/vruntime.conf b/conf/distro/vruntime.conf
index a10df80f..a489a7a2 100644
--- a/conf/distro/vruntime.conf
+++ b/conf/distro/vruntime.conf
@@ -7,8 +7,10 @@
 # This distro is used by multiconfig builds (vruntime-aarch64, vruntime-x86-64)
 # to create minimal rootfs images for QEMU-based container processing.
 #
-# The resulting images contain Docker or Podman tools and are used by
-# vrunner.sh to import containers during Yocto image builds.
+# IMPORTANT: This distro does NOT participate in CONTAINER_PROFILE.
+# The vdkr/vpdmn rootfs images explicitly specify their container stacks
+# to avoid conflicts between docker (runc) and podman (crun) requirements.
+# This allows both to be built in the same multiconfig.
 
 require conf/distro/poky.conf
 
@@ -45,3 +47,16 @@ VIRTUAL-RUNTIME_login_manager = ""
 
 # Keep images small - no documentation or debug
 EXTRA_IMAGE_FEATURES = ""
+
+# =============================================================================
+# Container runtime: NOT SET
+# =============================================================================
+# Unlike normal container distros, vruntime does NOT set CONTAINER_PROFILE
+# or VIRTUAL-RUNTIME_container_runtime. This prevents containerd/podman from
+# pulling a specific runtime via RDEPENDS, avoiding conflicts when both
+# vdkr (runc) and vpdmn (crun) are built in the same multiconfig.
+#
+# The vdkr-rootfs-image and vpdmn-rootfs-image recipes explicitly install
+# their required runtimes in IMAGE_INSTALL.
+# =============================================================================
+VIRTUAL-RUNTIME_container_runtime = ""