This repository was archived by the owner on May 12, 2021. It is now read-only.
This repository was archived by the owner on May 12, 2021. It is now read-only.
1.8.0-alpha0 containerd-shim-kata-v2 fails to start pod #1781
Description
Description of problem
in testing in Kubernetes, I see that 1.8.0-alpha0 release fails to start pod.
Expected result
It to work
Actual result
remote_runtime.go:105] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = failed to start sandbox container: failed to create containerd task: io.containerd.kata.v2: failed to connect: dial unix /run/containerd/containerd.sock.ttrpc: connect: no such file or directory
kuberuntime_sandbox.go:68] CreatePodSandbox for pod "nginx-deployment-qemu-7fc7f55446-9vf4v_default(6d2f8906-896d-11e9-9995-001e67569165)" failed: rpc error: code = Unknown desc = failed to start sandbox container: failed to create containerd task: io.containerd.kata.v2: failed to connect: dial unix /run/containerd/containerd.sock.ttrpc: connect: no such file or directory
This is a regression between 1.7.0 and 1.8.0-alpha0. I narrowed this down to the following commits:
eabfd99 shimv2: Improve shim shutdown logic
590ed09 vendor: update gogo/protobuf, containerd and agent vendors
I suggest we revert while getting help from @lifupan to root-cause.