Why do Kubernetes' containers fail when ran on runsc (gVisor) as a runtime in Docker?

9/20/2018

I am running a single master Kubernetes cluster with Docker. I wanted to try runsc (gVisor) on Kubernetes. I just wanted to start each container in a separate sandbox. So I set runsc as the default runtime and restarted the Docker service. To my surprise, all the Kubernetes' containers were failing (checked with docker ps). What is the exception that causes this? Is there any other way to use gVisor+Docker+Kubernetes?

I am using the right requirements to run each of them.

PS: I am just a beginner.

-- Adhil Roshan
docker
kubeadm
kubernetes
microservices

1 Answer

9/20/2018

Thanks for trying gVisor! Sorry it isn't working for you.

Running a Kubernetes Pod inside gVisor is still fairly experimental. It can be made to work, but is a bit difficult to configure right now. We are working to make this easier.

Can you run gVisor with Docker (not Kubernetes)? See the instructions here: https://github.com/google/gvisor#configuring-docker

If that fails, please file a bug report: https://github.com/google/gvisor/issues

If you can include debug logs, that will help us diagnose any failure. https://github.com/google/gvisor#debugging

-- Nicolas Lacasse
Source: StackOverflow