ImagePullBackOff: "Back-off pulling image \"gcr.io/google_containers/pause-amd64:3.0 解决方法

最新推荐文章于 2025-05-14 18:09:03 发布
最新推荐文章于 2025-05-14 18:09:03 发布
阅读量8.9k 收藏 2
点赞数 4
CC 4.0 BY-SA版权
分类专栏： java k8s 文章标签： k8s pod
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/Today_1st/article/details/83057066
本文介绍如何通过SSH进入Minikube环境，拉取并重新标记镜像，最终解决Pod无法正常运行的问题。涉及步骤包括SSH连接、镜像拉取、重新标记及重启Pod。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

首先进入minikube ssh模式：

[root@localhost resource-manifests]# minikube ssh

然后拉取镜像

docker@minikubeVM:~$ docker pull registry.cn-hangzhou.aliyuncs.com/google-containers/pause-amd64:3.0

最后打tag

docker@minikubeVM:~$ docker tag registry.cn-hangzhou.aliyuncs.com/google-containers/pause-amd64:3.0 gcr.io/google_containers/pause-amd64:3.0

最后退出

docker@minikubeVM:~$ exit

然后删除pod，重新创建就会使running状态了。

Kubernetes Pod报错 filed to get sandbox image “k8s.gcr.io/pause:3.6“
专注基础架构领域
12-06 4132
最近工作中在部署Pod后发现无法正常启动，查看Pod详情后看到以下报错信息： 问题的原因是因为调度的这台服务器上没有 k8s.gcr.io/pause:3.6 镜像，所以我们把镜像下载到这台服务器就可以了，执行命令： 到此 Kubernetes Pod报错 filed to get sandbox image "k8s.gcr.io/pause:3.6"问题解决。
Kubernetes：如何解决从k8s.gcr.io拉取镜像失败问题
完颜振江
01-17 2921
安装k8s的时候需要从k8s.gcr.io拉取镜像 kubeadm init --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=10.10.100.31 初始化的时候出现这个报错 [init] Using Kubernetes version: v1.21.0 [preflight] Running pre-flight checks [WARNING IsDockerSystemdCheck]: detected
rancher拉取harbor私有镜像失败,报错ImagePullBackOff: Back-off pulling image
代码改变世界！
12-12 1万+
rancher下的k8s拉取harbors私有镜像失败
在学习云原生的时候，一直会报错ImagePullBackOff Back-off pulling image
ganjiee0007的博客
03-01 1243
这个配置的镜像是不是可以自己直接下载，但是好像不怎么搜索得到。估计视频是21年前录制的，如今已是24年，老师不再维护当年的资源了。然后就在想，这个lfy_k8s_images到底是个啥玩意。在学习云原生的时候，一直会报错 （见最后几张图）最后恍然大悟，这个雷丰阳老师的大名！
为什么我不能获取到镜像，ImagePullBackoff
bacawa的博客
05-14 501
在Kubernetes部署过程中，可能会遇到Pod状态为ImagePullBackOff或Pending的问题，通常是由于镜像拉取失败或长时间处于等待状态，可以通过文章步骤排查和解决问题。
猫头虎分享云原生疑难杂Bug：ImagePullBackOff: Back-off pulling image “Libin9iOak-image:latest” 解决方案
GoCloudNative - 云原生技术的探索者。
08-10 1174
在日常的云原生开发过程中，容器镜像拉取问题是一个常见的痛点。当我们部署应用时，可能会遇到 ImagePullBackOff错误。这篇文章将 详细解读 ImagePullBackOff错误的原因，并提供详尽的解决步骤。通过实战案例，帮助你快速解决问题，提升开发效率。问题可能原因解决方法镜像拉取失败镜像名称错误检查并更新镜像名称镜像不存在镜像未推送推送镜像到正确的仓库认证失败没有配置认证信息配置 Docker Registry secret网络问题无法访问镜像仓库。
Back-off pulling image \"registry.access.redhat.com/rhel7/pod-infrastructure:latest
weixin_30822451的博客
01-06 1327
Error syncing pod, skipping: failed to "StartContainer" for "POD" with ImagePullBackOff: "Back-off pulling image \"registry.access.redhat.com/rhel7/pod-infrastructure:latest\""[root@master ~]#手动下载[r...
Back-off pulling image "registry.access.redhat.com/rhel7/pod-infrastructure:latest"
zhaikaiyun的博客
01-15 962
报错信息： Jan 14 12:26:57 k8snode01 kubelet: E0114 12:26:57.295735 8604 docker_manager.go:2159] Failed to create pod infra container: ErrImagePull; Skipping pod "nginx-3449338310-nmvsz_default(f67e741...
root@k8snode01-49 ~]# sudo kubeadm init --config=kubeadm-config.yaml [init] Using Kubernetes version: v1.25.0 [preflight] Running pre-flight checks [WARNING Hostname]: hostname "node" could not be reached [WARNING Hostname]: hostname "node": lookup node on 192.168.58.2: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' error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR ImagePull]: failed to pull image registry.k8s.io/kube-apiserver:v1.25.0: output: E0625 10:49:37.036283 7096 remote_image.go:171] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"registry.k8s.io/kube-apiserver:v1.25.0\": failed to resolve reference \"registry.k8s.io/kube-apiserver:v1.25.0\": failed to do request: Head \"https://us-west2-docker.pkg.dev/v2/k8s-artifacts-prod/images/kube-apiserver/manifests/v1.25.0\": dial tcp 74.125.199.82:443: connect: connection refused" image="registry.k8s.io/kube-apiserver:v1.25.0" time="2025-06-25T10:49:37+08:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"registry.k8s.io/kube-apiserver:v1.25.0\": failed to resolve reference \"registry.k8s.io/kube-apiserver:v1.25.0\": failed to do request: Head \"https://us-west2-docker.pkg.dev/v2/k8s-artifacts-prod/images/kube-apiserver/manifests/v1.25.0\": dial tcp 74.125.199.82:443: connect: connection refused" , error: exit status 1 [ERROR ImagePull]: failed to pull image registry.k8s.io/kube-controller-manager:v1.25.0: output: E0625 10:51:34.160244 7175 remote_image.go:171] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"registry.k8s.io/kube-controller-manager:v1.25.0\": failed to resolve reference \"registry.k8s.io/kube-controller-manager:v1.25.0\": failed to do request: Head \"https://us-west2-docker.pkg.dev/v2/k8s-artifacts-prod/images/kube-controller-manager/manifests/v1.25.0\": dial tcp 74.125.199.82:443: connect: connection refused" image="registry.k8s.io/kube-controller-manager:v1.25.0" time="2025-06-25T10:51:34+08:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"registry.k8s.io/kube-controller-manager:v1.25.0\": failed to resolve reference \"registry.k8s.io/kube-controller-manager:v1.25.0\": failed to do request: Head \"https://us-west2-docker.pkg.dev/v2/k8s-artifacts-prod/images/kube-controller-manager/manifests/v1.25.0\": dial tcp 74.125.199.82:443: connect: connection refused" , error: exit status 1 [ERROR ImagePull]: failed to pull image registry.k8s.io/kube-scheduler:v1.25.0: output: E0625 10:54:05.266959 7219 remote_image.go:171] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"registry.k8s.io/kube-scheduler:v1.25.0\": failed to resolve reference \"registry.k8s.io/kube-scheduler:v1.25.0\": failed to do request: Head \"https://us-west2-docker.pkg.dev/v2/k8s-artifacts-prod/images/kube-scheduler/manifests/v1.25.0\": dial tcp 74.125.199.82:443: connect: connection refused" image="registry.k8s.io/kube-scheduler:v1.25.0" time="2025-06-25T10:54:05+08:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"registry.k8s.io/kube-scheduler:v1.25.0\": failed to resolve reference \"registry.k8s.io/kube-scheduler:v1.25.0\": failed to do request: Head \"https://us-west2-docker.pkg.dev/v2/k8s-artifacts-prod/images/kube-scheduler/manifests/v1.25.0\": dial tcp 74.125.199.82:443: connect: connection refused" , error: exit status 1 [ERROR ImagePull]: failed to pull image registry.k8s.io/kube-proxy:v1.25.0: output: E0625 10:55:55.302433 7311 remote_image.go:171] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"registry.k8s.io/kube-proxy:v1.25.0\": failed to resolve reference \"registry.k8s.io/kube-proxy:v1.25.0\": failed to do request: Head \"https://us-west2-docker.pkg.dev/v2/k8s-artifacts-prod/images/kube-proxy/manifests/v1.25.0\": dial tcp 142.251.188.82:443: connect: connection refused" image="registry.k8s.io/kube-proxy:v1.25.0" time="2025-06-25T10:55:55+08:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"registry.k8s.io/kube-proxy:v1.25.0\": failed to resolve reference \"registry.k8s.io/kube-proxy:v1.25.0\": failed to do request: Head \"https://us-west2-docker.pkg.dev/v2/k8s-artifacts-prod/images/kube-proxy/manifests/v1.25.0\": dial tcp 142.251.188.82:443: connect: connection refused" , error: exit status 1 [ERROR ImagePull]: failed to pull image registry.k8s.io/pause:3.8: output: E0625 10:57:46.470991 7353 remote_image.go:171] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"registry.k8s.io/pause:3.8\": failed to resolve reference \"registry.k8s.io/pause:3.8\": failed to do request: Head \"https://us-west2-docker.pkg.dev/v2/k8s-artifacts-prod/images/pause/manifests/3.8\": dial tcp 142.251.188.82:443: connect: connection refused" image="registry.k8s.io/pause:3.8" time="2025-06-25T10:57:46+08:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"registry.k8s.io/pause:3.8\": failed to resolve reference \"registry.k8s.io/pause:3.8\": failed to do request: Head \"https://us-west2-docker.pkg.dev/v2/k8s-artifacts-prod/images/pause/manifests/3.8\": dial tcp 142.251.188.82:443: connect: connection refused" , error: exit status 1 [ERROR ImagePull]: failed to pull image registry.k8s.io/etcd:3.5.4-0: output: E0625 10:59:37.312592 7393 remote_image.go:171] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"registry.k8s.io/etcd:3.5.4-0\": failed to resolve reference \"registry.k8s.io/etcd:3.5.4-0\": failed to do request: Head \"https://us-west2-docker.pkg.dev/v2/k8s-artifacts-prod/images/etcd/manifests/3.5.4-0\": dial tcp 142.251.188.82:443: connect: connection refused" image="registry.k8s.io/etcd:3.5.4-0" time="2025-06-25T10:59:37+08:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"registry.k8s.io/etcd:3.5.4-0\": failed to resolve reference \"registry.k8s.io/etcd:3.5.4-0\": failed to do request: Head \"https://us-west2-docker.pkg.dev/v2/k8s-artifacts-prod/images/etcd/manifests/3.5.4-0\": dial tcp 142.251.188.82:443: connect: connection refused" , error: exit status 1 [ERROR ImagePull]: failed to pull image registry.k8s.io/coredns/coredns:v1.9.3: output: E0625 11:01:26.957404 7476 remote_image.go:171] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"registry.k8s.io/coredns/coredns:v1.9.3\": failed to resolve reference \"registry.k8s.io/coredns/coredns:v1.9.3\": failed to do request: Head \"https://us-west2-docker.pkg.dev/v2/k8s-artifacts-prod/images/coredns/coredns/manifests/v1.9.3\": dial tcp 142.251.188.82:443: connect: connection refused" image="registry.k8s.io/coredns/coredns:v1.9.3" time="2025-06-25T11:01:26+08:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"registry.k8s.io/coredns/coredns:v1.9.3\": failed to resolve reference \"registry.k8s.io/coredns/coredns:v1.9.3\": failed to do request: Head \"https://us-west2-docker.pkg.dev/v2/k8s-artifacts-prod/images/coredns/coredns/manifests/v1.9.3\": dial tcp 142.251.188.82:443: connect: connection refused" , error: exit status 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
最新发布
06-26
在kubeadm1.25版本中，coredns镜像的仓库路径已经改变（从k8s.gcr.io/coredns/coredns变为k8s.gcr.io/coredns/coredns），但实际拉取时，coredns的镜像在阿里云上可能还是放在google_containers下，且没有二级目录。...
使用kubeadm安装K8s
xuano0O的博客
02-25 1101
初始化master 初始化k8s并锁定v1.17.0版本。 kubeadm init \ --image-repository registry.cn-hangzhou.aliyuncs.com/google_containers \ --kubernetes-version v1.17.0 \ --pod-network-cidr=10.244.0.0/16 下载完成后使用【docker...
Ubuntu 20.04部署minikube配置不上阿里云的minikube镜像
哈哈虎的博客
11-25 5648
之前在 Ubuntu Server 18.04上部署 minikube Ubuntu 1804 部署minikube 启动指令 minikube start --image-mirror-country=cn 它会自动设置为阿里云镜像 直接会有提示 ... Using image repository registry.cn-hangzhou.aliyuncs.com/google_containers ... 但是在 Ubuntu Server 20.04 上死活不行,所以，很慢很慢，甚至..
Kubernetes 部署失败之 ErrImagePull&&ImagePullBackOff
洛洛devil的专栏
03-23 7万+
错误的容器镜像/非法的仓库权限解决方案： kubectl get pods 状态为ErrImagePull && ImagePullBackOff (一直在restarting) 当我们创建一个名字为myapp的deployment的时候，它指向的是一个不存在的docker镜像： 最常见的有两个问题： (a)指定了错误的容器镜像 (b)使用私有镜像却不提供仓库认证信息 ...
什么是 “ImagePullBackOff”？
长风破浪会有时的博客
04-15 1103
简单解释每个 Pod 在启动前需要从镜像仓库中下载所需的镜像。如果下载失败，Pod 状态就会显示“ImagePullBackOff”，意思是“镜像拉取被退回”或“暂时放弃拉取”。进一步解释Kubernetes 会不断尝试拉取镜像，经过多次失败后，它会暂停尝试，从而进入 “BackOff” 状态。镜像名称或标签错误：指定的镜像可能不存在。访问受限：如果使用私有镜像仓库，可能需要正确的认证信息。网络问题：容器所在的网络无法连接到镜像仓库。镜像仓库问题：镜像仓库本身故障或配置错误。
Kubernetes启动失败、Kubernetes的Pod节点出现ImagePullBackOff的可能原因以及解决方法
m0_74102771的博客
03-19 2448
通过修改镜像源、驱动的方式，使Kubernetes集群成功启动并运行Pod。
flannel ImagePullBackOff
mayi_xiaochaun的博客
03-03 1633
按照搭建Kubernetes时官网给的命令 kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml master节点flannel 拉取镜像失败 查看详细信息： kubectl describe pod kube-flannel-ds-xtfvq -n kube-system 打印如下： 解决方案1：node节点 pull成功，..
Kubernetes pod 状态出现 ImagePullBackOff 的原因
热门推荐
2007 年 ~ 2025 年，深耕 SAP 技术 18 年
03-02 11万+
通过一个试验作为例子来学习一下。 我们创建一个名为fail 的 deployment，让它故意指向一个实际并不存在的 Docker 镜像： $ kubectl run fail --image=jerry/sap:v1.0.0 查看这个Pod的状态，发现状态为 ErrImagePull 或者 ImagePullBackOff： $ kubectl get pods NAME ...
k8s pod状态 ImagePullBackOff
qq_15138049的博客
11-03 570
[root@hadoop03 hadoop]# kubectl get pods -o wide -n test NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES nginx 0/1 ImagePullBackOff 0 14m 10.
k8s拉取镜像失败处理 ImagePullBackOff ErrImageNeverPull
qq_45439217的博客
03-14 2万+
k8s拉取镜像失败处理
kubernetes集群Pod详细信息为Failed create pod sandbox，缺失镜像google_containers/pause-amd64.3.0解决方法
CycloneKid的博客
11-01 3157
在kubernetes集群上部署Pod时Pod的状态一直为ContainerCreating 使用命令kubectl describe pod podname查看Pod信息，显示Failed create pod sandbox. 使用命令journalctl -u kubelet -f查看系统日志中有关kubelet的信息 发现错误原因为Error response from daemon: ...
[root@master1 ~]# kubeadm config images pull --config kubeadm.yaml failed to pull image "registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0": output: E0715 01:48:45.987722 1704 remote_image.go:171] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0\": failed to resolve reference \"registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0\": failed to do request: Head \"https://registry.aliyuncs.com/v2/google_containers/kube-apiserver/manifests/v1.25.0\": dial tcp: lookup registry.aliyuncs.com on 10.0.0.2:53: read udp 10.0.0.81:55655->10.0.0.2:53: i/o timeout" image="registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0" time="2023-07-15T01:48:45-04:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0\": failed to resolve reference \"registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0\": failed to do request: Head \"https://registry.aliyuncs.com/v2/google_containers/kube-apiserver/manifests/v1.25.0\": dial tcp: lookup registry.aliyuncs.com on 10.0.0.2:53: read udp 10.0.0.81:55655->10.0.0.2:53: i/o timeout" , error: exit status 1 To see the stack trace of this error execute with --v=5 or higher 详细解释该报错
07-16
这个错误是由于在执行 `kubeadm config images pull` 命令时无法从指定的镜像仓库中拉取镜像引起的。具体报错信息显示了以下内容： ``` failed to pull image "registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0": output: E0715 01:48:45.987722 1704 remote_image.go:171] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0\": failed to resolve reference \"registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0\": failed to do request: Head \"https://registry.aliyuncs.com/v2/google_containers/kube-apiserver/manifests/v1.25.0\": dial tcp: lookup registry.aliyuncs.com on 10.0.0.2:53: read udp 10.0.0.81:55655->10.0.0.2:53: i/o timeout" image="registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0" time="2023-07-15T01:48:45-04:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0\": failed to resolve reference \"registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0\": failed to do request: Head \"https://registry.aliyuncs.com/v2/google_containers/kube-apiserver/manifests/v1.25.0\": dial tcp: lookup registry.aliyuncs.com on 10.0.0.2:53: read udp 10.0.0.81:55655->10.0.0.2:53: i/o timeout" , error: exit status 1 ``` 错误信息中提到了以下几个关键点： 1. `failed to resolve reference`：无法解析镜像引用，可能是由于网络问题导致无法访问指定的镜像仓库。 2. `dial tcp: lookup registry.aliyuncs.com on 10.0.0.2:53: read udp 10.0.0.81:55655->10.0.0.2:53: i/o timeout`：在解析镜像仓库地址时发生了 I/O 超时的错误。 根据这些信息，我推测可能有以下原因导致了这个问题： 1. 网络连接问题：可能是由于网络连接不稳定或者存在防火墙等限制，导致无法访问指定的镜像仓库。你可以尝试检查网络连接是否正常，以及是否有任何网络限制。 2. DNS 解析问题：可能是由于 DNS 解析失败导致无法解析指定的镜像仓库地址。你可以尝试检查 DNS 配置是否正确，并且能够正常解析该镜像仓库地址。 希望这些信息能帮助到你解决问题。如果有任何进一步的疑问，请随时提问。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值