Help needed to solve Minikube gvisor pod crash
26 views
Skip to first unread message
santhosh p
Mar 25, 2021, 8:59:19 AM3/25/21
to gVisor Users [Public]
Dear Team,
I am trying to configure a minikube with gvisor pod, but my pod is crashing continuesly, please help. OS is ubuntu 18.04.
ubuntu@gvisor-san:~$ kubectl get pod,runtimeclass gvisor -n kube-system
NAME READY STATUS RESTARTS AGE
pod/gvisor 0/1 CrashLoopBackOff 16 2d2h
NAME HANDLER AGE
runtimeclass.node.k8s.io/gvisor runsc 2d2h
Events:
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Pulled 63m (x34 over 3h48m) kubelet Container image "gcr.io/k8s-minikube/gvisor-addon:3@sha256:23eb17d48a66fc2b09c31454fb54ecae520c3e9c9197ef17fcb398b4f31d505a" already present on machine
Warning BackOff 53m (x729 over 3h47m) kubelet Back-off restarting failed container
Normal Pulling 48m kubelet Pulling image "gcr.io/k8s-minikube/gvisor-addon:3@sha256:23eb17d48a66fc2b09c31454fb54ecae520c3e9c9197ef17fcb398b4f31d505a"
Normal Pulled 48m kubelet Successfully pulled image "gcr.io/k8s-minikube/gvisor-addon:3@sha256:23eb17d48a66fc2b09c31454fb54ecae520c3e9c9197ef17fcb398b4f31d505a" in 2.915642498s
Normal Created 44m (x5 over 48m) kubelet Created container gvisor
Normal Started 44m (x5 over 48m) kubelet Started container gvisor
Normal Pulled 28m (x8 over 47m) kubelet Container image "gcr.io/k8s-minikube/gvisor-addon:3@sha256:23eb17d48a66fc2b09c31454fb54ecae520c3e9c9197ef17fcb398b4f31d505a" already present on machine
Warning BackOff 18m (x120 over 47m) kubelet Back-off restarting failed container
Normal SandboxChanged 12m kubelet Pod sandbox changed, it will be killed and re-created.
Normal Pulled 9m51s (x4 over 12m) kubelet Container image "gcr.io/k8s-minikube/gvisor-addon:3@sha256:23eb17d48a66fc2b09c31454fb54ecae520c3e9c9197ef17fcb398b4f31d505a" already present on machine
Normal Created 9m51s (x4 over 12m) kubelet Created container gvisor
Normal Started 9m51s (x4 over 12m) kubelet Started container gvisor
Warning BackOff 2m28s (x35 over 12m) kubelet Back-off restarting failed container
Fabricio Voznika
Mar 25, 2021, 7:18:05 PM3/25/21
to santhosh p, gVisor Users [Public]
Hi Santhosh,
What Kubernetes, Minikube and containerd versions are you using? Did you enable gVisor using the Minikube addon?
It's hard to tell what has failed from the logs above. To get more information you can enable debug logging following the these instructions: https://gvisor.dev/docs/user_guide/containerd/configuration/#debug
When creating the runsc.toml file, use the file below as not all the options in the link may be supported with older versions:
cat <<EOF | sudo tee /etc/containerd/runsc.toml
[runsc_config]
debug = "true"
debug-log = "/tmp/runsc/"
[runsc_config]
debug = "true"
debug-log = "/tmp/runsc/"
EOF
--
You received this message because you are subscribed to the Google Groups "gVisor Users [Public]" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gvisor-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gvisor-users/e67dc56c-d937-4bfd-a4f1-892492b80a77n%40googlegroups.com.
Ian Lewis
Mar 25, 2021, 8:49:34 PM3/25/21
to Fabricio Voznika, santhosh p, gVisor Users [Public]
It looks like the gvisor addon pod is crashing when trying to install it. Can you create a bug at gvisor.dev/issues/new and I'll take a look when I get a chance. Please include a bit more details about the version of minikube you're using and the commands you used to reproduce the problem.
To view this discussion on the web visit https://groups.google.com/d/msgid/gvisor-users/CAJdAnbkoJPSYAVNPKA_sSvjgdaW5g8ATNXrUQRBY-dAJRhEZSA%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages