欢迎来到尧图网

客户服务 关于我们

您的位置:首页 > 文旅 > 八卦 > K8S拉取busybox镜像时发生报错解决

K8S拉取busybox镜像时发生报错解决

2024/10/24 9:20:55 来源:https://blog.csdn.net/m0_66011019/article/details/139937821  浏览:    关键词:K8S拉取busybox镜像时发生报错解决

以下是报错信息

[root@k8s-master01 ~]# kubectl describe pod pod-base -n dev
Name:             pod-base
Namespace:        dev
Priority:         0
Service Account:  default
Node:             k8s-node01/192.168.58.130
Start Time:       Mon, 03 Jun 2024 16:37:04 +0800
Labels:           user=yoozoo
Annotations:      cni.projectcalico.org/containerID: 20a12171424dc2513d982efcc5760be9c7c4abe9f54d94bce8dd62dca83b7f60cni.projectcalico.org/podIP: 172.16.85.194/32cni.projectcalico.org/podIPs: 172.16.85.194/32
Status:           Pending
IP:               172.16.85.194
IPs:IP:  172.16.85.194
Containers:nginx:Container ID:   docker://93b76cbefd4512638353a0cfb9b1ba90d1e2e62e4225aa77711e0ba265fd3caeImage:          nginxImage ID:       docker-pullable://nginx@sha256:fad8e1cd52e24bce7b72cd7cb674a2efad671647b917055f5bd8a1f7ac9b1af8Port:           <none>Host Port:      <none>State:          TerminatedReason:       CompletedExit Code:    0Started:      Mon, 03 Jun 2024 16:38:00 +0800Finished:     Mon, 03 Jun 2024 17:15:57 +0800Ready:          FalseRestart Count:  0Environment:    <none>Mounts:/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-m847k (ro)busybox:Container ID:   Image:          busyboxImage ID:       Port:           <none>Host Port:      <none>State:          WaitingReason:       ImagePullBackOffReady:          FalseRestart Count:  0Environment:    <none>Mounts:/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-m847k (ro)
Conditions:Type              StatusInitialized       True Ready             False ContainersReady   False PodScheduled      True 
Volumes:kube-api-access-m847k:Type:                    Projected (a volume that contains injected data from multiple sources)TokenExpirationSeconds:  3607ConfigMapName:           kube-root-ca.crtConfigMapOptional:       <nil>DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300snode.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:Type     Reason          Age                 From               Message----     ------          ----                ----               -------Normal   Scheduled       60m                 default-scheduler  Successfully assigned dev/pod-base to k8s-node01Normal   Pulling         60m                 kubelet            Pulling image "nginx"Normal   Pulled          59m                 kubelet            Successfully pulled image "nginx" in 53.409s (53.409s including waiting)Normal   Created         59m                 kubelet            Created container nginxNormal   Started         59m                 kubelet            Started container nginxWarning  Failed          57m                 kubelet            Failed to pull image "busybox": error pulling image configuration: download failed after attempts=6: dial tcp 108.160.161.20:443: connect: connection refusedWarning  Failed          55m                 kubelet            Failed to pull image "busybox": error pulling image configuration: download failed after attempts=6: dial tcp 157.240.2.36:443: connect: connection refusedWarning  Failed          52m                 kubelet            Failed to pull image "busybox": error pulling image configuration: download failed after attempts=6: dial tcp 199.59.148.201:443: connect: connection refusedNormal   Pulling         51m (x4 over 59m)   kubelet            Pulling image "busybox"Warning  Failed          49m                 kubelet            Failed to pull image "busybox": error pulling image configuration: download failed after attempts=6: dial tcp 162.125.32.2:443: connect: connection refusedWarning  Failed          49m (x5 over 57m)   kubelet            Error: ImagePullBackOffWarning  Failed          49m (x4 over 57m)   kubelet            Error: ErrImagePullWarning  Failed          45m                 kubelet            Failed to pull image "busybox": error pulling image configuration: download failed after attempts=6: dial tcp 157.240.10.41:443: connect: connection refusedWarning  Failed          40m                 kubelet            Failed to pull image "busybox": error pulling image configuration: download failed after attempts=6: dial tcp 104.244.46.165:443: connect: connection refusedNormal   BackOff         30m (x56 over 57m)  kubelet            Back-off pulling image "busybox"Warning  Failed          25m                 kubelet            (combined from similar events): Failed to pull image "busybox": error pulling image configuration: download failed after attempts=6: dial tcp 65.49.68.152:443: connect: connection refusedNormal   SandboxChanged  25s (x43 over 21m)  kubelet            Pod sandbox changed, it will be killed and re-created.

解决方法:更换阿里云镜像,再次尝试下载

vi /etc/docker/daemon.json{"registry-mirrors":["https://6kx4zyno.mirror.aliyuncs.com"]
}

重启

systemctl daemon-reload
systemctl restart docker

版权声明:

本网仅为发布的内容提供存储空间,不对发表、转载的内容提供任何形式的保证。凡本网注明“来源:XXX网络”的作品,均转载自其它媒体,著作权归作者所有,商业转载请联系作者获得授权,非商业转载请注明出处。

我们尊重并感谢每一位作者,均已注明文章来源和作者。如因作品内容、版权或其它问题,请及时与我们联系,联系邮箱:809451989@qq.com,投稿邮箱:809451989@qq.com