easzlab.io.local:5000 can't access

[Hexiaopi]

What happened? 发生了什么问题？

Back-off pulling image "easzlab.io.local:5000/calico/cni:v3.26.4"

What did you expect to happen? 期望的结果是什么？

pod running

How can we reproduce it (as minimally and precisely as possible)? 尽可能最小化、精确地描述如何复现问题

docker pull easzlab.io.local:5000/calico/cni:v3.26.4
Error response from daemon: Get "https://easzlab.io.local:5000/v2/": EOF

Anything else we need to know? 其他需要说明的情况

No response

Kubernetes version k8s 版本

Client Version: v1.30.1 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.30.1

Kubeasz version

3.6.4

OS version 操作系统版本

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

Related plugins (CNI, CSI, ...) and versions (if applicable) 其他网络插件等需要说明的情况

[457352727]

你好，我也碰到了这个问题，找到解决办法了不

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[kevinniu666]

我也遇到这个问题了，使用的是离线的方式。K8S版本1.26.15，ezdown版本3.6.2,看起来是:5000的端口没有起

[kevinniu666]

看了一下源码，这个registry的服务是在./ezdown -D的时候启动的，我的环境是先在本地下载了以后再上传到服务器的。所以到了新的环境，这个服务在管理节点就没有启动了。解决这个问题只需要在运行Kubeasz的节点再执行一下./ezdown -D就会启动registry的容器并将5000端口host到宿主机上。

[y1li0]

是否配置了docker代理？我这边发生了同样的问题，首先是无法获取镜像，通过配置了docker代理，解决了镜像的问题。但随之而来的是无法推送到registry:5000，通过修改代理除外规则解决了推送的问题。
修改docker代理设置
vi /etc/systemd/system/docker.service.d/http-proxy.conf
代理使用的clash

[Service] Environment="HTTP_PROXY=192.168.1.4:7890" Environment="HTTPS_PROXY=192.168.1.4:7890" Environment="NO_PROXY=localhost,127.0.0.1,easzlab.io.local"
重启docker服务
systemctl daemon-reload systemctl restart docker

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[leeonfu]

HI, consider the issue is a feature, fix it by yourself.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.