Back to all scenarios
Scenario #39
Cluster Management
K8s v1.22, containerd switch

CRI Socket Mismatch Preventing kubelet Startup

kubelet failed to start after switching from Docker to containerd due to incorrect CRI socket path.

Find this helpful?
What Happened

The node image had containerd installed, but the kubelet still pointed to the Docker socket.

Diagnosis Steps
  • 1Checked kubelet logs for failed to connect to CRI socket.
  • 2Verified config file at /var/lib/kubelet/kubeadm-flags.env.
Root Cause

Wrong --container-runtime-endpoint specified.

Fix/Workaround
• Updated kubelet flags to point to /run/containerd/containerd.sock.
• Restarted kubelet.
Lessons Learned

CRI migration requires explicit config updates.

How to Avoid
  • 1Use migration scripts or kubeadm migration guides.
  • 2Validate container runtime on node bootstrap.
Previous ScenarioNext Scenario