**
https://blog.itwk.cc
由于國內(nèi)網(wǎng)絡(luò)原因，kubeadm init部署集群會卡住不動，，報錯如下：
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR ImagePull]: failed to pull image registry.k8s.io/kube-apiserver:v1.25.6: output: E0124 00:28:25.369652 3299 remote_image.go:171] “PullImage from image service failed” err=“rpc error: code = Unknown desc = Error response from daemon: Head “https://asia-east1-docker.pkg.dev/v2/k8s-artifacts-prod/images/kube-apiserver/manifests/v1.25.6”: dial tcp 64.233.189.82:443: connect: connection refused” image=“registry.k8s.io/kube-apiserver:v1.25.6”
time=“2023-01-24T00:28:25+08:00” level=fatal msg=“pulling image: rpc error: code = Unknown desc = Error response from daemon: Head “https://asia-east1-docker.pkg.dev/v2/k8s-artifacts-prod/images/kube-apiserver/manifests/v1.25.6”: dial tcp 64.233.189.82:443: connect: connection refused”
, error: exit status 1
截圖如下
![kubeadm init [ERROR ImagePull]: failed to pull image registry.k8s.io 解決方法](https://imgs.yssmx.com/Uploads/2023/06/508988-1.png)
解決方法
因為要下載K8s所需的Docker鏡像文件，眾所周知K8s是谷歌研發(fā)出來的，registry服務(wù)器在谷歌，國內(nèi)連不上，所以這里我們要用阿里云鏡像
運行kubeadm init時加上阿里云鏡像的參數(shù)即可
such as文章來源：http://www.zghlxwxcb.cn/news/detail-508988.html
kubeadm init --kubernetes-version=v1.25.6 --pod-network-cidr=10.224.0.0/16 --apiserver-advertise-address=172.25.80.10 --cri-socket unix:///var/run/cri-dockerd.sock --image-repository=registry.aliyuncs.com/google_containers
最后添加--image-repository=registry.aliyuncs.com/google_containers 即可文章來源地址http://www.zghlxwxcb.cn/news/detail-508988.html
到了這里，關(guān)于kubeadm init [ERROR ImagePull]: failed to pull image registry.k8s.io 解決方法的文章就介紹完了。如果您還想了解更多內(nèi)容，請在右上角搜索TOY模板網(wǎng)以前的文章或繼續(xù)瀏覽下面的相關(guān)文章，希望大家以后多多支持TOY模板網(wǎng)！
