【K8S】[remote_image.go:238] “PullImage from image service failed“拉取远程镜像失败

1.报错内容

[root@K8S1 work]#  crictl pull 192.168.1.11:443/myharbor/pause:3.6
E0720 12:39:23.318472   46758 remote_image.go:238] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"192.168.1.11:443/myharbor/pause:3.6\": failed to resolve reference \"192.168.1.11:443/myharbor/pause:3.6\": failed to do request: Head \"https://192.168.1.11:443/v2/myharbor/pause/manifests/3.6\": http: server gave HTTP response to HTTPS client" image="192.168.1.11:443/myharbor/pause:3.6"
FATA[0000] pulling image: rpc error: code = Unknown desc = failed to pull and unpack image "192.168.1.11:443/myharbor/pause:3.6": failed to resolve reference "192.168.1.11:443/myharbor/pause:3.6": failed to do request: Head "https://192.168.1.11:443/v2/myharbor/pause/manifests/3.6": http: server gave HTTP response to HTTPS client 

2.解决方法

需要添加远程镜像源的地址到端点。

--配置镜像加速器。
vi /etc/containerd/config.toml

[plugins."io.containerd.grpc.v1.cri"]
    [plugins."io.containerd.grpc.v1.cri".registry.mirrors."192.168.1.11:443"]
       endpoint = ["http://192.168.1.11:443"]
    [plugins."io.containerd.grpc.v1.cri".registry.configs."192.168.1.11:443".tls]
       insecure_skip_verify = false

3.重启所有的containerd 节点。

systemctl reload-daemon 

systemctl restart containerd 

4.重新拉取

[root@K8S1 work]# crictl pull 192.168.1.11:443/myharbor/nginx:latest
Image is up to date for sha256:605c77e624ddb75e6110f997c58876baa13f8754486b461117934b24a9dc3a85
[root@K8S1 work]# crictl images
IMAGE                             TAG                 IMAGE ID            SIZE
192.168.1.11:443/myharbor/nginx   latest              605c77e624ddb       56.7MB

问题在于ctr配置在文件/etc/containerd/config.toml中,需要将配置备份后改成以下配置:

  • 1
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
这个错误是由于在执行 `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、付费专栏及课程。

余额充值