From 061004dd233b3217c049aa8c83b68253a2114e17 Mon Sep 17 00:00:00 2001 From: Alex Lyn Date: Thu, 30 Apr 2026 18:27:47 +0800 Subject: [PATCH] tests: Use podsandbox sandboxer for the runc sanity check MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The check_daemon_setup function verifies that containerd + runc are functional before the real kata tests run. Using the shim sandboxer for this runc check hits a known containerd bug where the OCI spec is not populated before NewBundle is called, so config.json is never written and containerd-shim-runc-v2 fails at startup. See containerd/containerd#11640 The sandboxer choice is irrelevant for this sanity check, so use podsandbox which works correctly with runc. Signed-off-by: Fabiano Fidêncio Signed-off-by: Alex Lyn --- tests/integration/cri-containerd/integration-tests.sh | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/tests/integration/cri-containerd/integration-tests.sh b/tests/integration/cri-containerd/integration-tests.sh index 4c14e5219f..8c8851cb64 100755 --- a/tests/integration/cri-containerd/integration-tests.sh +++ b/tests/integration/cri-containerd/integration-tests.sh @@ -170,6 +170,13 @@ function err_report() { function check_daemon_setup() { info "containerd(cri): Check daemon works with runc" + # Use podsandbox for the runc sanity check: the shim sandboxer has a known + # containerd-side bug where the OCI spec is not populated before NewBundle is + # called, so config.json is never written and containerd-shim-runc-v2 fails. + # See https://github.com/containerd/containerd/issues/11640 + # This check only verifies that containerd + runc are functional before the + # real kata tests run, so the sandboxer choice doesn't matter here. + local SANDBOXER="podsandbox" create_containerd_config "runc" # containerd cri-integration will modify the passed in config file. Let's