Error: failed to run Kubelet: unable to determine runtime API version: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix: missing address

[devbiu]

What keywords did you search in kubeadm issues before filing this one?

issues: #1893

Is this a BUG REPORT

Versions

kubeadm version (use kubeadm version): 1.24.7

Environment:

• Kubernetes version (use kubectl version): 1.24.7
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release): centos8
• Kernel (e.g. uname -a): Linuxxxxxx 4.18.0-240.el8.x86_64 kubeadm join on slave node fails preflight checks #1 SMP Wed Sep 23 05:13:10 EDT 2020 x86_64 x86_64 x86_64 GNU/Linux
• Container runtime (CRI) (e.g. containerd, cri-o): cri-docker
• Container networking plugin (CNI) (e.g. Calico, Cilium): cni
• Others:

What happened?

kubeadm init --kubernetes-version=1.24.7 --cri-socket unix:///run/cri-dockerd.sock --v=5 

systemctl status kubelet

Error: failed to run Kubelet: unable to determine runtime API version: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix: missing address

crictl --runtime-endpoint unix:///run/cri-dockerd.sock logs CONTAINERID

Because the error reasons are the same, I tried all the methods in the issues, but still can't solve my problem.
issues: #1893

What you expected to happen?

kubernetes successful installation

How to reproduce it (as minimally and precisely as possible)?

kubeadm init --kubernetes-version=1.24.7 --cri-socket unix:///run/cri-dockerd.sock --v=5 

Anything else we need to know?

before executing issues, runtime error
issues: kubernetes/registry.k8s.io#266 (comment)

[neolit123]

unix:///run/cri-dockerd.sock

k8s maintainers recommend switching to containerd or crio. they are more up to date with k8s...

this is not a kubeadm bug, per se.

[neolit123]

/support

[github-actions]

Hello, @devbiu 🤖 👋

You seem to have troubles using Kubernetes and kubeadm.
Note that our issue trackers should not be used for providing support to users.
There are special channels for that purpose.

Please see:

• https://github.com/kubernetes/kubeadm#support