You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The confidential container was installed successfully, but when starting the pod with the runtimeclass as kata-qemu-tdx, it failed. The error message is as follows:
Failed to create pod sandbox: rpc error: code = NotFound desc = failed to create containerd task: failed to create shim task: /opt/kata/share/defaults/kata-containers/configuration-qemu-tdx.toml: file /run/containerd/io.containerd.runtime.v2.task/k8s.io/a767929c7272b6f72c8d5da9ffaf88e0ea07d1b40e4ebc8c23ff44cb84463d3f/PLACEHOLDER_FOR_DISTRO_QEMU_WITH_TDX_SUPPORT does not exist: not found
lscpu |grep 'tdx_guest' and ls /dev/tdx_guest is success
k8s version:v1.30.8
containerd version:v1.7.24
kata version:3.9.0
operator version: v.0.10
pod yaml
apiVersion: v1
kind: Pod
metadata:
name: nginx-kata-tdx
labels:
app.kubernetes.io/name: MyNginxTdx
spec:
runtimeClassName: kata-qemu-tdx
containers:
The confidential container was installed successfully, but when starting the pod with the runtimeclass as kata-qemu-tdx, it failed. The error message is as follows:
Failed to create pod sandbox: rpc error: code = NotFound desc = failed to create containerd task: failed to create shim task: /opt/kata/share/defaults/kata-containers/configuration-qemu-tdx.toml: file /run/containerd/io.containerd.runtime.v2.task/k8s.io/a767929c7272b6f72c8d5da9ffaf88e0ea07d1b40e4ebc8c23ff44cb84463d3f/PLACEHOLDER_FOR_DISTRO_QEMU_WITH_TDX_SUPPORT does not exist: not found
lscpu |grep 'tdx_guest' and ls /dev/tdx_guest is success
k8s version:v1.30.8
containerd version:v1.7.24
kata version:3.9.0
operator version: v.0.10
pod yaml
apiVersion: v1
kind: Pod
metadata:
name: nginx-kata-tdx
labels:
app.kubernetes.io/name: MyNginxTdx
spec:
runtimeClassName: kata-qemu-tdx
containers:
image: swr.cn-north-4.myhuaweicloud.com/ddn-k8s/docker.io/nginx:1.27.3
ports:
The text was updated successfully, but these errors were encountered: