《Kubernetes 排错指南-006》error execution phase couldn‘t initialize a Kubernetes cluster
系统环境:
- VMware ESXi 7.0.2
- Ubuntu 20.04 LTS
- Docker 20.10.8
- Kubernetes 1.22.1
- Node: master
执行命令:
$ kubeadm init
报错如下:
Unfortunately, an error has occurred:timed out waiting for the conditionThis 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.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
报错说明:
这个问题一般是由虚拟机或软件包配置错误错误引起的,需要修改 Docker Cgroup
的驱动程序。
解决方案:
$ vi /etc/docker/daemon.json{"exec-opts": ["native.cgroupdriver=systemd"],"log-driver": "json-file","log-opts": {"max-size": "100m"},"storage-driver": "overlay2","storage-opts": ["overlay2.override_kernel_check=true"],"registry-mirrors" : ["https://ot2k4d59.mirror.aliyuncs.com/"],"graph": "/data/docker"
}$ systemctl daemon-reload
$ systemctl restart docker
将 Docker Cgroup
驱动程序修改为 systemd
然后加载配置,重新启动 Docker
服务。
《Kubernetes 排错指南-006》error execution phase couldn‘t initialize a Kubernetes cluster相关推荐
- k8s入坑之报错(11)添加node节点报错:error execution phase preflight: [preflight] Some fatal errors occurred:...
参考文档:wangzy-Zj-Kubernetes 加入主节点报错 报错信息: [root@localhost ~]# kubeadm join 192.168.1.112:6443 --token ...
- [K8S]error execution phase preflight: couldn‘t validate the identity of the API Server
用kubeadm工具,k8s使用kubeadm join将工作节点加入到主控节点的时候遇到如下问题,执行命令卡顿很久后报错 [root@k8s2 ~]# kubeadm join 192.168.0. ...
- error execution phase preflight: couldn‘t validate the identity of the API Server: Get
关于K8S服务搭建本人用的云服务分别是:华为云.百度云.阿里云 Running pre-flight checks error execution phase preflight: couldn't ...
- Worker节点加入K8S集群报错:error execution phase preflight: couldn‘t validate the identity of the API Server
问题描述 在使用kubeadm的join命令,想要将Worker节点加入到K8S集群,命令如下: kubeadm join cluster-endpoint:6443 --token x5g4uy.w ...
- error execution phase preflight: couldn‘t validate the identity of the API Server: abort connecting
在使用k8s的过程中,相信很多人都遇到过使用kubeadm join命令,将node加入master时,出现error execution phase preflight: couldn't vali ...
- kubernetes权威指南_如何快速上手成为大厂标配的kubernetes?
程序员书库(ID:CodingBook) 猿妹 综合整理 过去几年,以docker.kubernetes为代表的容器技术已发展为一项通用技术,BAT.滴滴.京东.头条等大厂,都争相把容器和k8s项目作 ...
- 《Kubernetes 排错指南-010》Error parsing HTTP 413 response body: 413 Request Entity Too Large
系统环境: Ubuntu 20.04 LTS Docker 20.10.8 Kubernetes 1.22.1 Node: master.worker 问题描述: docker-registry在 K ...
- k8s join 集群报错之error execution phase kubelet-start: error uploading crisocket:
[问题描述1] 主节点上误删了/etc/kubernetes下的文件,当做kubeadm init的时候,找不到对应的key文件 invalid or incomplete external CA: ...
- node重新加入error execution phase kubelet-start: error uploading crisocket: Unauthorized
报错内容如下 [root@k8s-node1 ~]# swapoff -a [root@k8s-node1 ~]# kubeadm reset [reset] WARNING: Changes mad ...
最新文章
- java两个线程同时运行_java如何几乎同时结束两个线程
- 谷歌放弃python-老大离开Google,去了Dropbox
- 如何在PHP中保护数据库密码?
- PowerShell-4.API调用以及DLL调用
- 上海事业评中级职称还要考计算机,上海职称评审-事业单位如何评职称
- 计算机的微程序存放在dram,计算机组成与结构
- 【2016年第4期】欧盟数据可携权评析
- OpenCV--实现图像滑动窗口截取子图操作
- 淘宝 NPM 镜像解决软件下载速度慢的问题
- Oracle通过身份证求年龄的方法
- CAD迷你画图中文版
- Unity3D Editor Undo回退效果实现3 Odin相关
- 小米10开始抓取日志怎么关闭_日志MIUI 10 9.5.22 内测更新资讯
- craps 双骰子源码c语言,双骰子(Craps)规则及其玩法二(转)
- PAT甲级 1087 条条大路通罗马
- 伽罗华域(Galois Field)理解、基于伽罗华域的四则运算(附详细python代码)
- icheck结合datatable使用方法及实现全选、反选功能
- 谷歌地图下载器中“地图艺术照”
- IBM ServerGuide 9.40
- 除了office,常用的办公软件还有这些