0

When I used kubectl apply -f pod.yaml, I found that the corresponding pod did not succeed

When I use kubectl describe pod nginx-sandbox-ori it shows

Successfully assigned default/nginx-sandbox-ori to localhost.localdomain
Container image "xxx" already present on machine
Created container alpine
Error: failed to create containerd task: failed to create shim task: failed to mount "/run/kata-containers/shared/containers/alpine/rootfs" to "/run/kata-containers/alpine/rootfs",with error: ENOENT: No such file or directory: unknown

I use kata-container as container runtime And I started a kind as RuntimeClass, set the name as kata

“/run/kata-containers/shared/containers/alpine/rootfs” I found that this folder does not exist on the machine

Tovi
  • 1
  • 1
  • forget it, In the confidential container solution, you cannot directly pull the image to the local through other tools – Tovi Mar 24 '23 at 09:34
  • Did you find a solution to this problem? I'm having the same issue. I checked `/run/kata-containers/shared/`. It does not have any directory `containers`. It only has a directory called `sandboxes`. Do we have to pull and unpack the image manually on the node for this to work? – Kapil Pendse Jun 23 '23 at 16:25

0 Answers0