二个服务器是一核2g的配置不够
紧急重新购买二个，计费的，腾讯云 销毁时间下午四点40
好的
出现新的错误-docker版本调高了，部署不了怎么办
This issue can be solved by installing conntract
sudo apt-get install -y conntrack socat
此方法没用
Docker 版本降级为经过验证的版本 20.0
[WARNING SystemVerification]: this Docker version is not on the list of validated versions: 23.0.1. Latest validated version: 20.10
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR FileContent–proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables contents are not set to 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
降级就
sudo yum downgrade docker-ce-20.10.* docker-ce-cli-20.10.* containerd.io
docker version
出错了
Transaction check error:
file /usr/libexec/docker/cli-plugins/docker-buildx from install of docker-ce-cli-1:20.10.23-3.el7.x86_64 conflicts with file from package docker-buildx-plugin-0:0.10.2-1.el7.x86_64
Error Summary
删除冲突的“docker-buildx-plugin
sudo yum remove docker-buildx-plugin
sudo yum downgrade docker-ce-20.10.* docker-ce-cli-20.10.* containerd.io
emoved:
containerd.io.x86_64 0:1.6.18-3.1.el7
Installed:
containerd.io.x86_64 0:1.6.16-3.1.el7
Complete!
[root@VM-0-2-centos ~]#
出现新问题了
docker降级失败
为什么呢？原因是估计环境有啥问题，直接卸载全部docker删除相关文件
然后yum-config-manager –add-repo http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
后yum install docker-ce 20.10
安装验证版本
新错误
[preflight] Running pre-flight checks
[WARNING SystemVerification]: this Docker version is not on the list of validated versions: 23.0.1. Latest validated version: 20.10
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR FileContent–proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables contents are not set to 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
sudo sysctl net.bridge.bridge-nf-call-iptables=1
kubeadm reset 重置
搞定
Your Kubernetes control-plane has initialized successfully!
To start using your cluster, you need to run the following as a regular user:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
Alternatively, if you are the root user, you can run:
export KUBECONFIG=/etc/kubernetes/admin.conf
You should now deploy a pod network to the cluster.
Run “kubectl apply -f [podnetwork].yaml” with one of the options listed at:
https://kubernetes.io/docs/concepts/cluster-administration/addons/
Then you can join any number of worker nodes by running the following on each as root:
kubeadm join 10.206.0.2:6443 –token soyl0r.9092x5518g5decit \
–discovery-token-ca-cert-hash sha256:1c2b8dc1a5c552072511bb0e9a5c000f320c9696fcb739463bdb356479d7e630
