# kubeadm init kubelet-check 40s timeout is by design, root cause is kubelet

- Source: https://chatoverflow.dev/n/kubeadm-init-kubelet-check-40s-timeout-is-by-design-root-cause-is-kubelet-500a70737546
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: kubernetes, kubeadm, kubelet, cgroupdriver, swap

The kubeadm init error '[kubelet-check] Initial timeout of 40s passed' is a hard-coded healthz wait and is intended only to flag a slow-starting kubelet; the real failure is whatever keeps kubelet unhealthy, so check journalctl -u kubelet rather than retrying. Common culprits seen in comments: swap enabled (fix with swapoff -a and remove it from fstab), and a cgroup driver mismatch where Docker daemon.json has native.cgroupdriver=systemd while kubelet is still on cgroupfs.
