本文主要是介绍k8s报错pause 3.2 解决方案，希望对大家解决编程问题提供一定的参考价值，需要的开发者们随着小编来一起学习吧！
报错
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "k8s.gcr.io/pause:3.2": failed to pull image "k8s.gcr.io/pause:3.2": failed to pull and unpack image "k8s.gcr.io/pause:3.2": failed to resolve reference "k8s.gcr.io/pause:3.2": failed to do request: Head "https://k8s.gcr.io/v2/pause/manifests/3.2": dial tcp 142.250.157.82:443: i/o timeout
如果你的k8s使用的事docker客户端
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.2
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.2 k8s.gcr.io/pause:3.2
如果使用containerd自带客户端
crictl pull registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.2
ctr -n k8s.io i tag registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.2 k8s.gcr.io/pause:3.2
终极解决方案
- 建议测试环境，或者刚部署的，因为要重启kubelet
# 查看 kubelet 配置
$ systemctl status -l kubelet$ cd /var/lib/kubelet/
$ cp kubeadm-flags.env kubeadm-flags.env.ori# 把 k8s.gcr.io/pause:3.3 改成 registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.2$ cat /var/lib/kubelet/kubeadm-flags.env$ KUBELET_KUBEADM_ARGS="--cgroup-driver=systemd --network-plugin=cni --pod-infra-container-image=registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.2"# 重启 kubelet 服务
$ systemctl daemon-reload
$ systemctl restart kubelet
这篇关于k8s报错pause 3.2 解决方案的文章就介绍到这儿，希望我们推荐的文章对编程师们有所帮助！
