crio on in KIC uses different runtime than ISO ("open /run/runc: no such file or directory")

[medyagh]

we need to investigate why on docker driver with crio runtime many tests fail with
"msg="open /run/runc: no such file or directory"

The same tests passes on VM drivers (ISO)

example test log
https://storage.googleapis.com/minikube-builds/logs/22301/42985/Docker_Linux_crio.html#fail_TestStartStop%2fgroup%2fold-k8s-version%2fserial%2fEnableAddonWhileActive

-- /stdout --
** stderr ** 
	X Exiting due to MK_ADDON_ENABLE_PAUSED: enabled failed: check paused: list paused: runc: sudo runc list -f json: Process exited with status 1
	stdout:
	
	stderr:
	time="2025-12-25T19:01:33Z" level=error msg="open /run/runc: no such file or directory"

Maybe there is a Path Isseu in Kicbase?

[medyagh]

#KIC

$ crio config | grep default_runtime

default_runtime = "crun"

docker@minikube:~$ crio version
Version: 1.34.3

VM

$ crio config | grep default_runtime

default_runtime = "runc"

$ crio version
INFO[2025-12-26 00:39:33.461096541Z] Starting CRI-O, version: 1.29.1, git: unknown(clean)
Version: 1.29.1

We might just wanna make the ISO and KIC have matching CRIO version.