sudo kubeadm init --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=192.168.56.2
Found multiple CRI endpoints on the host. Please define which one do you wish to use by setting the ‘criSocket’ field in the kubeadm configuration file:
unix:///var/run/containerd/containerd.sock, unix:///var/run/cri-dockerd.sock
To see the stack trace of this error execute with --v=5 or higher
I’ve no idea this correct place to ask question.
I tried following the lecture and able implement with runtime as containerd.io. Now I’m trying with docker but getting two run time, 1) conatinerd.io 2) cri-dockerd ( plugin). As per documentation cri-dockerd sholud not be running. I tried both but unable execule kubeadm init
HI @akamal1981
As you are installed multiple CRI, you need to specify which one you have to use by adding the --cri-socket
on init command.
- Pull container images:
# if you want to use Containerd
sudo kubeadm config images pull --cri-socket unix:///var/run/containerd/containerd.sock
# or
# if you want to use Docker
sudo kubeadm config images pull --cri-socket unix:///var/run/cri-dockerd.sock
- Init with kubeadm
# if you want to use Containerd
sudo kubeadm init --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=192.168.56.2 --cri-socket unix:///var/run/containerd/containerd.sock
# or
# if you want to use Docker
sudo kubeadm init --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=192.168.56.2 --cri-socket unix:///var/run/cri-dockerd.sock
Regard