Open visheshtanksale opened 3 days ago
cc: @zvonkok
@littlejawa is this something you're helping with or are you looking for reinforcements?
@haircommander Yes, he is helping with that, and we're currently out of options and need reinforcements.
what happens when you create the container with a different oci runtime?
what happens when you create the container with a different oci runtime?
Non kata containers are created successfully.
The symptom is similar to what we saw with kata 3.3.0, where the content of the container's rootfs was not accessible to the runtime. We fixed it in our own CI by adding the flag "storage.overlay.skip_mount_home=true" in crio's config. I'm also fixing it in the same way in the crio CI for kata, in https://github.com/cri-o/cri-o/pull/7958.
In this cluster the flag was not there, so we added it, but it didn't solve the problem. Could crio ignore the flag for some reason? What else could cause the same symptom?
What happened?
Setup Kata using kata deploy on CRI-O. When creating a test pod I get error below
If I try to bring up any other container using kata-qemu runtime I get similar error that the command which is entrypoint of the container is not found
Attached crio log here Attached kata log here
Qemu and kata version are below
Opened an issue on kata-containers @littlejawa suggest adding the storage overlay config
But this doesnt help.
What did you expect to happen?
The pod should come up without error
How can we reproduce it (as minimally and precisely as possible)?
kata-qemu
runtime classAnything else we need to know?
No response
CRI-O and Kubernetes version
OS version
Additional environment details (AWS, VirtualBox, physical, etc.)