锐客网

  1. 首页 > 睿知 > it技术 > >

快速解决Kubernetes从k8s.gcr.io仓库拉取镜像失败问题

IT知识Kubernetes

休言女子非英物，夜夜龙泉壁上鸣。这篇文章主要讲述快速解决Kubernetes从k8s.gcr.io仓库拉取镜像失败问题相关的知识，希望能为你提供帮助。

前言：?在部署Kubernetes的过程中，需要从k8s.grc.io仓库中拉取部署所需的镜像文件，但是由于国内对国外的防火墙问题导致无法正常拉取，下面介绍一个方法来解决此问题，完成Kubernetes的正常部署。
问题描述：?使用Kubernetes V1.22.1版本部署Kubernetes集群，在进行kubeadm init初始化时，需要从k8s.grc.io仓库拉取所需的镜像：

......
[preflight/images] You can also perform this action in beforehand using \'kubeadm config images pull\'
[preflight] Some fatal errors occurred:
[ERROR ImagePull]: failed to pull image [k8s.gcr.io/kube-apiserver-amd64:v1.22.1]: exit status 1
[ERROR ImagePull]: failed to pull image [k8s.gcr.io/kube-controller-manager-amd64:v1.22.1]: exit status 1
[ERROR ImagePull]: failed to pull image [k8s.gcr.io/kube-scheduler-amd64:v1.22.1]: exit status 1
[ERROR ImagePull]: failed to pull image [k8s.gcr.io/kube-proxy-amd64:v1.22.1]: exit status 1
[ERROR ImagePull]: failed to pull image [k8s.gcr.io/pause:3.5]: exit status 1
[ERROR ImagePull]: failed to pull image [k8s.gcr.io/etcd-amd64:3.5.0]: exit status 1
[ERROR ImagePull]: failed to pull image [k8s.gcr.io/coredns:1.8.4]: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`


解决方案：???报错案例（使用相同方法解决）：javascript:void(0)??
?docker.io仓库对google的容器做了镜像，可以通过下列命令下拉取相关镜像：

docker pull mirrorgooglecontainers/kube-apiserver-amd64:v1.22.1
docker pull mirrorgooglecontainers/kube-controller-manager-amd64:v1.22.1
docker pull mirrorgooglecontainers/kube-scheduler-amd64:v1.22.1
docker pull mirrorgooglecontainers/kube-proxy-amd64:v1.22.1
docker pull mirrorgooglecontainers/pause:3.5
docker pull mirrorgooglecontainers/etcd-amd64:3.5.0
docker pull coredns/coredns:1.8.4


?拉取的镜像版本信息需要根据部署Kubernetes V1.22.1版本所需的实际情况进行相应的修改（即将下载下来的镜像标签版本信息改成kubeadm init初始化要求的镜像版本标签信息）。通过docker tag命令来修改镜像的标签：

docker tag docker.io/mirrorgooglecontainers/kube-proxy-amd64:v1.22.1 k8s.gcr.io/kube-proxy-amd64:v1.22.1
docker tag docker.io/mirrorgooglecontainers/kube-scheduler-amd64:v1.22.1 k8s.gcr.io/kube-scheduler-amd64:v1.22.1
docker tag docker.io/mirrorgooglecontainers/kube-apiserver-amd64:v1.22.1k8s.gcr.io/kube-apiserver-amd64:v1.22.1
docker tag docker.io/mirrorgooglecontainers/kube-controller-manager-amd64:v1.22.1 k8s.gcr.io/kube-controller-manager-amd64:v1.22.1
docker tag docker.io/mirrorgooglecontainers/etcd-amd64:3.5.0k8s.gcr.io/etcd-amd64:3.5.0
docker tag docker.io/mirrorgooglecontainers/pause:3.5k8s.gcr.io/pause:3.5
docker tag docker.io/coredns/coredns:1.8.4k8s.gcr.io/coredns:1.8.4


?使用docker rmi删除不用的镜像，通过docker images命令显示，已经有我们需要的镜像文件，可以继续部署工作了：

[root@k8s-master ~]#docker images
REPOSITORYTAGIMAGE IDCREATEDSIZE
k8s.gcr.io/kube-proxy-amd64v1.22.1bea694275d971 days ago97.8 MB
k8s.gcr.io/kube-scheduler-amd64v1.22.1ca43b177bese1 days ago56.8 MB
k8s.gcr.io/kube-apiserver-amd64v1.22.13de571b6587b1 days ago187 MB
coredns/coredns1.8.4b3154sdrecfc1 days ago45.6 MB
k8s.gcr.io/coredns1.8.4b3b94275d97c1 days ago45.6 MB
k8s.gcr.io/etcd-amd643.5.0b8d1f5sa24f71 days ago219 MB
k8s.gcr.io/pause3.5d6csa23rdsa11 days ago742 kB


?重新初始化Kubernetes

[root@k8s-master ~]# kubeadm init --kubernetes-version=v1.22.1 --apiserver-advertise-address=192.168.1.18 --image-repository registry.aliyuncs.com/google0.0/16
[init] Using Kubernetes version: v1.22.1
[preflight] Running pre-flight checks
[WARNING Service-Docker]: docker service is not enabled, please run \'systemctl enable docker.service\'
[WARNING Hostname]: hostname "k8s-master" could not be reached
[WARNING Hostname]: hostname "k8s-master": lookup k8s-master on 192.168.1.1:53: no such host
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using \'kubeadm config images pull\'
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [k8s-master kubernetes kubernetes.default kubernetes.default.svc kubernetes.defa
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [k8s-master localhost] and IPs [192.168.1.18 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [k8s-master localhost] and IPs [192.168.1.18 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". Th
[apiclient] All control plane components are healthy after 6.002108 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.22" in namespace kube-system with the configuration for the kubelets in the cluster
[upload-certs] Skipping phase. Please see --upload-certs
[mark-control-plane] Marking the node k8s-master as control-plane by adding the labels: [node-role.kubernetes.io/master(deprecated) nod
[mark-control-plane] Marking the node k8s-master as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
[bootstrap-token] Using token: 9t2nu9.00ieyfqmc50dgub6
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to get nodes
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate cre
[bootstrap-token] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstrap-token] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
[kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key
[addons] Applied essential addon: CoreDNS
[addons] Applied essential addon: kube-proxy

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 192.168.1.18:6443 --token 9t2nu9.00ieyfqmc50dgub6 \\
--discovery-token-ca-cert-hash sha256:183b6c95b4e49f0bd4074c61aeefc56d70215240fbeb7a633afe3526006c4dc9


?初始化成功，问题解决！
↓↓↓↓↓↓?最近刚申请了个微信公众号，上面也会分享一些运维知识，大家点点发财手关注一波，感谢大家。 ??【原创公众号】：非著名运维 【福利】：公众号回复 “资料” 送运维自学资料大礼包哦！??
快速解决Kubernetes从k8s.gcr.io仓库拉取镜像失败问题

文章图片


【快速解决Kubernetes从k8s.gcr.io仓库拉取镜像失败问题】

    推荐阅读


    上一篇：CentOS7搭建Cacti监控平台

    下一篇：如何在WordPress中以帖子类型插入附件并更新自定义字段