sysbox icon indicating copy to clipboard operation
sysbox copied to clipboard

Can't schedule dind pod with sysbox 0.6.1 on kubernetes 1.24.2

Open TH3VenGeuR opened this issue 1 year ago • 5 comments

Hello my fresh cluster with sysbox 0.6.1 is not able to schedule any pods with the error below :

Warning FailedCreatePodSandBox 13s (x19 over 4m1s) kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = RuntimeHandler "sysbox-runc" not supported

Node OS : Ubuntu 20.04.3 LTS kernel 5.4.0-1055-kvm Kubelet Version: v1.24.2 Kube-Proxy Version: v1.24.2 kubelet image : hyperkube:v1.24.2-rancher

Can you help ?

TH3VenGeuR avatar Apr 12 '23 13:04 TH3VenGeuR

Hi @TH3VenGeuR,

From the error it seems K8s does not know about the sysbox runtime, so likely the installation failed.

What K8s distro are you using?

Where you able to install Sysbox on the cluster via the sysbox-deploy-k8s daemonset?

ctalledo avatar Apr 14 '23 18:04 ctalledo

The installation logs of the daemonset sysbox-k8s-deploy says everything went good. I am using rancher to deploy k8s.

TH3VenGeuR avatar Apr 14 '23 19:04 TH3VenGeuR

Thanks @TH3VenGeuR; since this is Rancher, let me put this on @rodnymolina plate, as he is familiar with Rancher K8s.

Rodny is on vacation so he will likely answer sometime next week.

ctalledo avatar Apr 14 '23 19:04 ctalledo

Hi @TH3VenGeuR, could you please provide the following after issue is reproduced?

  • kubectl get all -A
  • kubectl get nodes -o wide
  • Provide the spec of the failing pod

Thanks!

rodnymolina avatar Apr 18 '23 18:04 rodnymolina

Here are all the requested informations :

https://paste.chapril.org/?43bcabfac20ba410#7SvUdSphPrE4fh43UTJGJ3qTKxiuxEknrVqTvahVkmEH

https://paste.chapril.org/?91fe58780eeb8aa5#Ae9UaHwzEpMKfgYkDU8XcWX3S2pRFhdZ4jZ7VqRk6fjk

https://paste.chapril.org/?24c0f09a5751b4e7#87RqQ5Fv2BebmrdtDAB9LJQhjiJqWhem8tKAzG95gj4e

We can also chat on slack if it help

TH3VenGeuR avatar Apr 19 '23 08:04 TH3VenGeuR