v3.1.0 离线部署，Unable to find image 'registry:2' locally

liketoochao

[root@localhost kubesphere-all-v3.1.0-offline-linux-amd64]# ./kk init os -f xiangxun.yaml -s ./dependencies/ –add-images-repo
INFO[08:24:55 CST] Init operating system
INFO[08:24:56 CST] Start initializing kubesphere-02 [193.169.100.51] node=193.169.100.51
INFO[08:24:56 CST] Start initializing kubesphere-04 [193.169.100.53] node=193.169.100.53
INFO[08:24:56 CST] Start initializing kubesphere-03 [193.169.100.52] node=193.169.100.52
INFO[08:24:57 CST] Start initializing kubesphere-05 [193.169.100.54] node=193.169.100.54
INFO[08:24:57 CST] Start initializing kubesphere-01 [193.169.100.50] node=193.169.100.50
INFO[08:24:57 CST] Start initializing kubesphere-06 [193.169.100.55] node=193.169.100.55
Push /root/kubesphere-all-v3.1.0-offline-linux-amd64/dependencies/centos-7-amd64-rpms.tar.gz to 193.169.100.52:/tmp Done
Push /root/kubesphere-all-v3.1.0-offline-linux-amd64/dependencies/centos-7-amd64-rpms.tar.gz to 193.169.100.51:/tmp Done
Push /root/kubesphere-all-v3.1.0-offline-linux-amd64/dependencies/centos-7-amd64-rpms.tar.gz to 193.169.100.54:/tmp Done
Push /root/kubesphere-all-v3.1.0-offline-linux-amd64/dependencies/centos-7-amd64-rpms.tar.gz to 193.169.100.55:/tmp Done
Push /root/kubesphere-all-v3.1.0-offline-linux-amd64/dependencies/centos-7-amd64-rpms.tar.gz to 193.169.100.53:/tmp Done
Push /root/kubesphere-all-v3.1.0-offline-linux-amd64/dependencies/centos-7-amd64-rpms.tar.gz to 193.169.100.50:/tmp Done
INFO[08:30:47 CST] Complete initialization kubesphere-03 [193.169.100.52] node=193.169.100.52
INFO[08:30:50 CST] Complete initialization kubesphere-02 [193.169.100.51] node=193.169.100.51
INFO[08:30:57 CST] Complete initialization kubesphere-04 [193.169.100.53] node=193.169.100.53
INFO[08:31:31 CST] Complete initialization kubesphere-01 [193.169.100.50] node=193.169.100.50
INFO[08:32:09 CST] Complete initialization kubesphere-05 [193.169.100.54] node=193.169.100.54
INFO[08:32:10 CST] Complete initialization kubesphere-06 [193.169.100.55] node=193.169.100.55
WARN[08:32:12 CST] Task failed …
WARN[08:32:12 CST] error: Unable to find image ‘registry:2’ locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [:
See ‘docker run –help’.
: exit status 125
Error: Failed to init operating system: Unable to find image ‘registry:2’ locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [:
See ‘docker run –help’.
: exit status 125
Usage:
kk init os [flags]

Flags:
–add-images-repo Create a local images registry
-f, –filename string Path to a configuration file
-h, –help help for os
-s, –sources string Path to the dependencies’ dir

Global Flags:
–debug Print detailed information (default true)
–in-cluster Running inside the cluster

Failed to init operating system: Unable to find image ‘registry:2’ locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [:
See ‘docker run –help’.
: exit status 125
[root@localhost kubesphere-all-v3.1.0-offline-linux-amd64]# cd ..
[root@localhost ~]#

Cauchy

liketoochao

不要加 –add-images-repo 这个需要那个registry的镜像

需要kk启动仓库的话 ./kk init registry -f xxx.yaml

liketoochao

Cauchy 我试试，有详细的3.1部署文档吗？应该和3.0 有区别的

liketoochao

Cauchy
执行 ./kk init registry -f xxx.yaml 后，创建了这样的registry 的仓库

[root@kubesphere-01 kubesphere-all-v3.1.0-offline-linux-amd64]# ps -ef|grep registry
root 20261 1 0 08:06 ? 00:00:00 /usr/local/bin/registry serve /etc/kubekey/registry/config.yaml
root 20569 20548 0 08:11 ? 00:00:00 registry serve /etc/docker/registry/config.yml
root 20763 14275 0 08:16 pts/1 00:00:00 grep –color=auto registry
[root@kubesphere-01 kubesphere-all-v3.1.0-offline-linux-amd64]#

谢谢

liketoochao

./kk init registry -f xxx.yaml , 只是导入一个registry 镜像吗？不启动仓库服务？

以下是导入image的错误：
The push refers to repository [dockerhub.kubekey.local/kubesphere/fluentbit-operator]
Get https://dockerhub.kubekey.local/v2/: dial tcp 193.169.100.50:443: connect: connection refused
kubesphere/fluent-bit:v1.6.9
dockerhub.kubekey.local/kubesphere/fluent-bit:v1.6.9

registry 的docker服务没有启动

Feynman

liketoochao 3.1 和 3.0 的离线安装没有太大区别，注意把版本号换一下，只是导入的镜像不一样而已。

视频：https://www.bilibili.com/video/BV1Pz4y1C7jr
文档：https://kubesphere.com.cn/docs/installing-on-linux/introduction/air-gapped-installation/

Feynman

liketoochao 3.1 和 3.0 的离线安装没有太大区别，注意把版本号换一下，只是导入的镜像不一样而已。

视频：https://www.bilibili.com/video/BV1Pz4y1C7jr
文档：https://kubesphere.com.cn/docs/installing-on-linux/introduction/air-gapped-installation/

liketoochao

仔细看了半天， ./kk init registry -f xxx.yaml 没有load registry 的镜像，也没用创建 registry 的容器，只是完美的跳过了这一步？

liketoochao

[root@kubesphere-01 certs.d]# pwd
/etc/docker/certs.d
[root@kubesphere-01 certs.d]# ls
dockerhub.kubekey.local dockerhub.kubekey.local:5000
[root@kubesphere-01 certs.d]#

liketoochao

安装过程中，pull镜像一直报错

Jun 29 09:03:25 kubesphere-02 dockerd: time=“2021-06-29T09:03:25.409757016+08:00” level=warning msg=“Error getting v2 registry: Get https://dockerhub.kubekey.local/v2/: x509: certificate signed by unknown authority”
Jun 29 09:03:25 kubesphere-02 dockerd: time=“2021-06-29T09:03:25.409803894+08:00” level=info msg=“Attempting next endpoint for pull after error: Get https://dockerhub.kubekey.local/v2/: x509: certificate signed by unknown authority”
Jun 29 09:03:25 kubesphere-02 dockerd: time=“2021-06-29T09:03:25.409982277+08:00” level=error msg=“Handler for POST /v1.40/images/create returned error: Get https://dockerhub.kubekey.local/v2/: x509: certificate signed by unknown authority”

尝试添加

{
“insecure-registries”: [“dockerhub.kubekey.local:5000”]
}

未解决