-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
containerd: failed to run kubelet: unknown service runtime.v1alpha2.RuntimeService #3471
Comments
Here's the call where kubelet kills itself: Dec 18 21:20:00 minikube kubelet[3391]: F1218 21:20:00.445512 3391 server.go:233] failed to run Kubelet: failed to create kubelet: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService |
I haven't tried yet, but I wonder if setting |
It's working with v0.31.0. Thanks Priya for the help! |
commenting out disabled_plugins = ["cri"] is feasible |
in /etc/containerd/config.toml |
Refer to this link https ://github.com/containerd/containerd/issues/4581 |
BUG REPORT
Environment:
minikube version: v0.30.0
OS:
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
VM driver:
"DriverName": "kvm2",
ISO version
"Boot2DockerURL": "file:///home/fvoznika/.minikube/cache/iso/minikube-v0.30.0.iso",
"ISO": "/home/fvoznika/.minikube/machines/minikube/boot2docker.iso",
What happened:
Error running:
How to reproduce it (as minimally and precisely as possible):
Not really sure how to get into this state, but once it does, minikube cannot start anymore.
Output of
minikube logs
(if applicable):minikube start output:
minikube.log
Last few lines from minikube logs
minikube ssh
minikube delete && rm -rf .minikube && rm -rf .kube
doesn't fix the problem.minikube start --vm-driver=kvm2
works.The text was updated successfully, but these errors were encountered: