Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gvisor addon should survive minikube restart #3443

Closed
balopat opened this issue Dec 11, 2018 · 0 comments · Fixed by #3445
Closed

gvisor addon should survive minikube restart #3443

balopat opened this issue Dec 11, 2018 · 0 comments · Fixed by #3445

Comments

@balopat
Copy link
Contributor

balopat commented Dec 11, 2018

After enabling gvisor in minikube, stopping the VM and restarting it with the same args below the gvisor addon fails to create pods as Failed create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox runtime: no runtime for untrusted workload is configured. The containerd/config.toml is overriden by the restart. Also minikube addons list shows gvisor as enabled.

minikube start --container-runtime=containerd \
               --docker-opt containerd=/var/run/containerd/containerd.sock \
               --network-plugin=cni \
               --disk-size 30g \
               --vm-driver=hyperkit               

current workaround:

minikube addons disable gvisor
minikube addons enable gvisor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant