It's a known limitation that QEMU based runtime classes will not work with Kind or Minikube, leading to:
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 42s default-scheduler Successfully assigned default/nginx-kata-qemu to minikube
Warning FailedCreatePodSandBox 9s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create containerd task: failed to create shim task: Failed to Check if grpc server is working: rpc error: code = DeadlineExceeded desc = timed out connecting to vsock 3189232285:1024: unknown
This needs further debug in order to get to the root cause of the issue, and potentially to a fix. However, for now, we should make sure that we document such limitation.
It's a known limitation that QEMU based runtime classes will not work with Kind or Minikube, leading to:
This needs further debug in order to get to the root cause of the issue, and potentially to a fix. However, for now, we should make sure that we document such limitation.
One issue already reported about this is https://github.com/confidential-containers/operator/issues/124, and that's also been observed by Pradipta during the early tests of v0.1.0.
Signed-off-by: Fabiano Fidêncio fabiano.fidencio@intel.com