failed to pull image k8s.gcr.io/kube-apiserver:v1.14.1: output: Error response from daemon:

最新推荐文章于 2024-05-08 13:31:09 发布
原创 最新推荐文章于 2024-05-08 13:31:09 发布 · 1.0k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

针对kubeadm初始化过程中遇到的k8s.gcr.io镜像拉取失败问题，提供了一种解决方案：从Dockerhub获取所需版本的镜像。执行命令包括指定kubernetes版本、pod网络CIDR和服务CIDR，并忽略Swap检查。

背景：kubeadam init 出错，这也是因为某种神秘的力量导致的k8s.gcr.io连接不上.

解决办法： 从dockerhub上收集

执行：

kubeadm init --kubernetes-version=v1.14.1 --pod-network-cidr=10.244.0.0/16 --service-cidr=10.96.0.0/12 --ignore-preflight-errors=Swap
kubeadm init 报错：failed to pull image “k8s.gcr.io/kube-apiserver:v1.20.15“: output: Error response fr
小石潭记丶
06-09 1482
问题由于国内网络原因，kubeadm init会卡住不动，一卡就是半个小时，然后报出这种问题：完整的错误日志如下：原因显而易见，是因为要下载k8s.gcr.io的docker镜像，但是国内连不上https://k8s.gcr.io/v2/。还有其它问题参考。
[Kubernets 相关镜像下载遇到]failed to pull image “k8s.gcr.io/kube-apiserver:v1.22.0“: output: Error response
grown_Liu的博客
11-29 4370
问题原因： https://k8s.gcr.io/v2/国内无法访问。 我们执行：kubeadm config images pull --config=init.default.yaml用于抓取镜像。 该指令依赖两个数据： /etc/docker/daemon.json 作用：用于设定docker pull 时使用的加速URL 注意：如果在daemon.json文件中进行配置，需要docker版本高于1.12.6(在这个版本上不生效) 官方的配置地址：https://docs.docker.com/en
kubeadm init ：failed to pull image [k8s.gcr.io/kube-apiserver-amd64:v1.11.1
海鸥
01-10 1016
问题描述 [root@localhost ~]# kubeadm init --kubernetes-version=v1.11.1 --pod-network-cidr=10.244.0.0/16 --service-cidr=10.96.0.0/12 在进行k8s集群初始化的时候，报以下错误： [preflight] Some fatal errors occurred: [ERROR Im...
k8s集群初始化报错： [ERROR ImagePull]: failed to pull image k8s.gcr.io/coredns:1.6.5: output: Error response
weixin_58652725的博客
04-07 771
因为网络问题导致报错，加上--image-repository=registry.aliyuncs.com/google_containers，就可以啦。执行完以下命令后会报错。
Kubernetes k8s拉取镜像失败最简单最快最完美解决方法 [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver
热门推荐
weixin_43168190的博客
07-09 7万+
问题 由于国内网络原因，kubeadm init会卡住不动，一卡就是半个小时，然后报出这种问题： [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.18.5: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Time
手动安装高可用k8s集群（二进制）v1.23.4版本
闹着玩儿的博客
02-22 1万+
kubernetes（k8s）高可用集群，二进制方式部署，版本v1.23.4，nginx+keepalived
Kubernetes系列：k8s 1.14单节点安装
Gordon_luo的博客
06-19 2776
01前言 最近k8s很火，相信大家都听过。那什么是k8s呢？Kubernetes狭义的说：它是一个开源的容器集群管理系统，可以实现容器集群的自动化部署、自动扩缩容、维护等功能。下面我们来测试一下搭建单节点k8s。 本文转自我个人的公众号：天目星 ，请大家多多关注。 请关注我的微信公众号 一、使用的软件与架构图 linux：CentOS 7....
K8S在ubuntu上的部署流程
qq_41955670的博客
09-18 1020
K8S在ubuntu上的部署流程 1.配置： 环境：ubuntu 16.04 节点： 192.168.25.22 master 192.168.25.33 node 2.系统设置（master和node都执行） 1）禁用swap swapoff -a 2）关闭防火墙 systemctl stop firewalld systemctl disable firewalld 3）禁用Selinux apt install selinux-utils setenforce 0 4）在两个节点的/etc/h
Kubernetes——Kubernetes1.14的安装
卑微小韩
11-18 1048
文章目录Kubernetes——Kubernetes的安装一、k8s的安装1.1、k8s的4种安装部署方式离线安装包下载地址1.2、安装前准备（使用kubeadmin通过离线镜像安装）1.2.1、准备集群服务器1.2.1 配置服务器免密操作1.2.1.1 Master服务器1.2.1.1.1 生成公钥与私钥对1.2.1.2 其他服务器的操作1.2.1.3 测试1.2.2、设置主机名与时区（Master、Node）1.2.3、添加hosts网络主机配置（Master、Node1、Node2）1.2.4、关闭防
部署k8s集群+k8s架构，基础概念
hjyhjy0的博客
11-01 482
部署k8s集群 基本环境：CentOS 7.6 CPU:双核 MEM： 2G 环境 IP地址 master 192.168.1.20 node01 192.168.1.21 node02 192.168.1.22 这里安装的k8s版本为1.15.0版本，docker部署安装指定版本18.9.0 3个node节点时间必须同步 [root@localhost ~]# yum -y install ntp [root@localhost ~]# systemctl start ntpd
k8s.gcr.io/kube-apiserver:v1.12.2
11-01
使用方法请关注blog: https://blog.csdn.net/wenwst docker load < kube-apiserver.v1.12.2.tar docker tag 51a9c329b7c5 k8s.gcr.io/kube-apiserver:v1.12.2
k8s.gcr.io/kube-apiserver:v1.17.3镜像包
03-06
kubernetes的k8s.gcr.io/kube-apiserver:v1.17.3镜像包，版本为v1.17.3。文件是kube-controller-manager_v_1_17.3.tar
kubeadm init 出错：[ERRORImagePull]：failed to pull image k8s.gcr.io.
zhyysj01的博客
05-31 1020
访问镜像超时。
Mac 安装 Minikube 及解决 “[ERROR ImagePull]: failed to pull image“ 问题
日常学习与专研的记录
12-26 3654
本文介绍如何在 Mac 上安装 Minikube，成功拉起 K8s 集群，以及解决 "[ERROR ImagePull]: failed to pull image" 问题。
kubernetes： Failed to pull image...rpc error: code = Canceled desc = context canceled
feiger的专栏
09-03 4万+
背景： 部署deployment服务之后，pod拉起失败， describe 显示code = Canceled desc = context canceled 分析： 1.查看harbor，排除网络问题 2.服务器上可以 docker pull ，排除image问题 3.查看pull image policy 为 IfNotPresent 排除镜像策略问题 4.查看 pod日志，code = ...
Failed to pull image xxx unauthorized: authentication required
f的博客
06-19 2327
在执行完kubectl create deployment后执行kubectl describe pod发现出错了，错误描述： Failed to pull image "xxx": unauthorized: authentication required 解决方法，删除deployment和pod后重新执行kubectl create deployment
kubeadm init 失败: failed to pull image k8s.gcr.io/etcd:3.4.13-0
张伯毅的专栏
08-25 1452
因为k8s.gcr.io镜像库在国内需要翻墙，所以普通下载无法成功完成，可以更改一下下载的镜像库地址为国内地址，下载后将标签打回和kubeadm config一致的方法解决。
猫头虎分享已解决Bug || Kubernetes节点镜像拉取失败Failed to pull image from gcr.io/google_containers/猫头虎
GoCloudNative - 云原生技术的探索者。
05-08 1236
大家好，猫头虎又来了！今天我们要讨论的是Kubernetes节点镜像拉取失败的问题。在部署或启动Kubernetes集群时，如果看到Failed to pull image from gcr.io/google_containers/猫头虎的错误信息，通常是因为连接不到Google的GCR容器镜像仓库，导致无法拉取节点镜像。这篇博客将详细介绍如何切换到国内的镜像仓库，如阿里云、腾讯云或华为云的Kubernetes镜像加速器，以确保Kubernetes节点镜像可以顺利下载，保持集群正常运行。
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
k8s.gcr.io/kube-apiserver:v1.25.0 k8s.gcr.io/kube-controller-manager:v1.25.0 k8s.gcr.io/kube-scheduler:v1.25.0 k8s.gcr.io/kube-proxy:v1.25.0 k8s.gcr.io/pause:3.8 k8s.gcr.io/etcd:3.5.4-0 k8s.gcr.io/...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值