Open kristi-balla opened 1 day ago
If you install containerd from Docker, it includes configuration to disable the CRI plugin:
/etc/containerd/config.toml
# Copyright 2018-2020 Docker Inc.
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
# http://www.apache.org/licenses/LICENSE-2.0
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
disabled_plugins = ["cri"]
It does not happen with the default containerd configuration, from https://containerd.io
https://kubernetes.io/docs/setup/production-environment/container-runtimes/#containerd
Another alternative is to use Docker as the container runtime, with the cri-dockerd daemon.
You can use crictl
(and ctr
) for your troubleshooting, installing Kubernetes assumes that it works OK.
containerd config default > /etc/containerd/config.toml systemctl restart containerd crictl version
Version: 0.1.0
RuntimeName: containerd
RuntimeVersion: 1.6.20~ds1
RuntimeApiVersion: v1
What Happened?
I was setting up a minikube cluster on AWS via
minikube start --cni=calico --driver=none --container-runtime=containerd
and keep getting this error:validate service connection: validate CRI v1 runtime API for endpoint \"unix:///run/containerd/containerd.sock\": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService
I am completely baffled as to why this happened.
With
--alsologtostderr
:I need calico to define some network policies in my cluster. Thus far, I've tried the following:
minikube start --cni=calico
--> works flawlesslyminikube start --cni=calico --driver=none
--> also works flawlesslyminikube start --cni=calico --driver=none --container-runtime=containerd
--> refuses to play nice. I did notice in the logs that the mix of the none driver and containerd runtime is untested, so I would be grateful for any help/hint provided!I am running the latest versions of docker and kubernetes on a debian bookworm machine.
Attach the log file
Operating System
Other
Driver
None (Baremetal)