From a4cd368b40d5f95d759548e45475d62555b08cf5 Mon Sep 17 00:00:00 2001 From: Bruce Ashfield Date: Mon, 6 Apr 2026 15:49:32 +0000 Subject: k3s-host: set virtual-runc as container runtime The k3s-host container profile had VIRTUAL-RUNTIME_container_runtime set to empty, which meant no OCI runtime (runc or crun) was installed. containerd's RDEPENDS uses this variable to pull in the runtime, so k3s pods failed with "runc: executable file not found in $PATH". Set to virtual-runc which is what k3s expects. The k3s-node profile inherits from k3s-host so it gets the fix too. Signed-off-by: Bruce Ashfield --- conf/distro/include/meta-virt-container-k3s-host.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/distro/include/meta-virt-container-k3s-host.inc b/conf/distro/include/meta-virt-container-k3s-host.inc index 166d7cf1..f92cb956 100644 --- a/conf/distro/include/meta-virt-container-k3s-host.inc +++ b/conf/distro/include/meta-virt-container-k3s-host.inc @@ -1,7 +1,7 @@ include meta-virt-container.inc VIRTUAL-RUNTIME_container_engine ?= "" -VIRTUAL-RUNTIME_container_runtime ?= "" +VIRTUAL-RUNTIME_container_runtime ?= "virtual-runc" VIRTUAL-RUNTIME_container_networking ?= "" VIRTUAL-RUNTIME_container_dns ?= "" VIRTUAL-RUNTIME_container_orchestration ?= "k3s-host" -- cgit v1.2.3-54-g00ecf