Linux下minikube启动失败(It seems like the kubelet isn‘t running or healthy)(1)_it seems like the kubelet isn't running or healthy-CSDN博客

本文链接：https://blog.csdn.net/m0_60721649/article/details/138656293

先自我介绍一下，小编浙江大学毕业，去过华为、字节跳动等大厂，目前在阿里

深知大多数程序员，想要提升技能，往往是自己摸索成长，但自己不成体系的自学效果低效又漫长，而且极易碰到天花板技术停滞不前！

因此收集整理了一份《2024年最新Linux运维全套学习资料》，初衷也很简单，就是希望能够帮助到想自学提升又不知道该从何学起的朋友。

既有适合小白学习的零基础资料，也有适合3年以上经验的小伙伴深入学习提升的进阶课程，涵盖了95%以上运维知识点，真正体系化！

由于文件比较多，这里只是将部分目录截图出来，全套包含大厂面经、学习笔记、源码讲义、实战项目、大纲路线、讲解视频，并且后续会持续更新

需要这份系统化的资料的朋友，可以点击这里获取！

This error is likely caused by:

The kubelet is not running
The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:

‘systemctl status kubelet’
‘journalctl -xeu kubelet’

Additionally, a control plane component may have crashed or exited when started by the container runtime.

To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker.

Here is one example how you may list all Kubernetes containers running in docker:

‘docker ps -a | grep kube | grep -v pause’

Once you have found the failing container, you can inspect its logs with:

‘docker logs CONTAINERID’

error execution phase wait-control-plane: couldn’t initialize a Kubernetes cluster

running command: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable–etc-kubernetes-manifests,DirAvailable–data-minikube,FileAvailable–etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable–etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable–etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable–etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap

.: exit status 1

Sorry that minikube crashed. If this was unexpected, we would love to hear from you:

https://github.com/kubernetes/minikube/issues/new

看上面的问题像是kubelet启动失败了，执行命令tail /var/log/messages查看进一步的原因：

Jun 8 09:45:35 minikube kubelet: F0608 09:45:35.392302 24268 server.go:266] failed to run Kubelet: failed to create kubelet: misconfiguration: kubelet cgroup driver: “cgroupfs” is different from docker cgroup driver: “systemd”

Jun 8 09:45:35 minikube systemd: kubelet.service: main process exited, code=exited, status=255/n/a

Jun 8 09:45:35 minikube systemd: Unit kubelet.service entered failed state.

Jun 8 09:45:35 minikube systemd: kubelet.service failed.

上述日志表明：kubelet的cgroup driver是cgroupfs，docker的 cgroup driver是systemd，两者不一致导致kubelet启动失败。

解决问题

尝试过修改kubelet的cgroup dirver(文件位置：/etc/systemd/system/kubelet.service.d/10-kubeadm.conf)，但是每次启动minikube时会被覆盖掉，于是只能放弃这种处理方式，转去修改docker的cgroup dirver设置；
打开文件/usr/lib/systemd/system/docker.service，如下图，将红框中的systemd改为cgroupfs：

在这里插入图片描述

重新加载配置信息，重启服务：

systemctl daemon-reload && systemctl restart docker

完成了上述修改，再去重新启动minikube就可以成功了，如下：

[root@minikube ~]# minikube delete

Uninstalling Kubernetes v1.14.3 using kubeadm …
Deleting “minikube” from none …
The “minikube” cluster has been deleted.

[root@minikube ~]# minikube start --vm-driver=none

minikube v1.1.1 on linux (amd64)
Creating none VM (CPUs=2, Memory=2048MB, Disk=20000MB) …
Configuring environment for Kubernetes v1.14.3 on Docker 1.13.1
Unable to load cached images: loading cached images: loading image /root/.minikube/cache/images/gcr.io/k8s-minikube/storage-provisioner_v1.8.1: stat /root/.minikube/cache/images/gcr.io/k8s-minikube/storage-provisioner_v1.8.1: no such file or directory
Pulling images …
Launching Kubernetes …
Configuring local host environment …