实例化
kubeadm init --config=kubeadm.yaml --ignore-preflight-errors=SystemVerification
报错
[init] Using Kubernetes version: v1.25.0
[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:[ERROR CRI]: container runtime is not running: output: time="2024-05-27T14:24:00+08:00" level=fatal msg="validate service connection: CRI v1 runtime API is not implemented for endpoint \"unix:///run/containerd/containerd.sock\": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService"
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher
看报错提示CRI v1 runtime API is not implemented for endpoint "unix:///run/containerd/containerd.sock，报错说明containerd 没有启动，我们看下containerd 状态
crictl info
FATA[0000] validate service connection: CRI v1 runtime API is not implemented for endpoint "unix:///run/containerd/containerd.sock": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService
systemctl status containerd
● containerd.service - containerd container runtimeLoaded: loaded (/usr/lib/systemd/system/containerd.service; enabled; vendor preset: disabled)Active: active (running) since Sat 2024-05-25 15:00:45 CST; 1 day 23h agoDocs: https://containerd.ioProcess: 17742 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)Main PID: 17744 (containerd)Tasks: 10Memory: 16.4MCGroup: /system.slice/containerd.service└─17744 /usr/bin/containerdMay 25 15:00:45 node4 containerd[17744]: time="2024-05-25T15:00:45.244945213+08:00" level=error m...gin"
May 25 15:00:45 node4 containerd[17744]: time="2024-05-25T15:00:45.245036348+08:00" level=info ms...l.v1
May 25 15:00:45 node4 containerd[17744]: time="2024-05-25T15:00:45.245143134+08:00" level=info ms...c.v1
May 25 15:00:45 node4 containerd[17744]: time="2024-05-25T15:00:45.245165036+08:00" level=info ms...c.v1
May 25 15:00:45 node4 containerd[17744]: time="2024-05-25T15:00:45.245596769+08:00" level=info ms...ices
May 25 15:00:45 node4 containerd[17744]: time="2024-05-25T15:00:45.245678125+08:00" level=info ms...ice"
May 25 15:00:45 node4 containerd[17744]: time="2024-05-25T15:00:45.245791893+08:00" level=warning...s\""
May 25 15:00:45 node4 containerd[17744]: time="2024-05-25T15:00:45.246066102+08:00" level=info ms...trpc
May 25 15:00:45 node4 containerd[17744]: time="2024-05-25T15:00:45.246138980+08:00" level=info ms...sock
May 25 15:00:45 node4 containerd[17744]: time="2024-05-25T15:00:45.246224876+08:00" level=info ms...99s"
Hint: Some lines were ellipsized, use -l to show in full.
可以看error里面是由错误的。
journalctl -fu containerd
May 25 15:00:45 node4 containerd[17744]: time="2024-05-25T15:00:45.245678125+08:00" level=info msg="Connect containerd service"
May 25 15:00:45 node4 containerd[17744]: time="2024-05-25T15:00:45.245791893+08:00" level=warning msg="failed to load plugin io.containerd.grpc.v1.cri" error="failed to create CRI service: failed to find snapshotter \"overlayfs\""
这里说明系统不支持overlayfs
lsmod | grep overlay
overlay 91659 0
xfs_info /
从docker 官方文档上面来看
如果要修改xfs ftyoe 要修改设置，可是如果修改这个设计影响系统，所以暂时启动这个服务器
