Vishesh Tanksale
Vishesh Tanksale
cc: @zvonkok
> what happens when you create the container with a different oci runtime? Non kata containers are created successfully.
@littlejawa I didnt have the storage option param. But adding that doesnt help. Still hitting the same error
@littlejawa I did reload crio service. This is the config change ``` # cat /etc/crio/crio.conf.d/99-kata-deploy | grep -A 3 -B 1 storage_option [crio] storage_option = [ "overlay.skip_mount_home=true", ] ``` I...
I tried to completely wipe the CRIO storage and test it again. But no success. I dont see anything obvious in the CRIO logs Attached kata-collect-data.sh output [here](https://github.com/user-attachments/files/15927139/kata.log) CRIO Logs...
I did try that. Its coming up with appropriate configs. ``` Current CRI-O configuration:\n[crio]\n root = \"/var/lib/containers/storage\"\n runroot = \"/run/containers/storage\"\n imagestore = \"\"\n storage_driver = \"overlay\"\n storage_option = [\"overlay.skip_mount_home=true\"]\n ```...
> > Are you on RHEL? May be that might be causing different behaviors? > > Most of my testing is done on Ubuntu 22.04.4, but without kubernetes - just...
@littlejawa How do you install kata on your setup? I am trying to figure out whats the difference between your setup and the kata-deploy setup.
Can you please provide the logs from the device plugin daemonset pod to triage why is it in `CrashLoopBackOff`state?
@jnirmalraj Can you please provide some details of the dcgm exporter pod like describing the pods and getting its logs