因外网原因，k8s.gcr.io 镜像拉取失败。是否可以通过国内镜像站 来去初始化kubeadm呢--image-repository

[itxiao6]

问题基础描述
按照提示排查 应该是kubeadm config images pull拉取镜像时，因为k8s.gcr.io 网络不可达 导致的失败

Error

2022-09-01 21:11:05 [EROR] Applied to cluster error: failed to init init master0 failed, error: failed to execute command(kubeadm init --config=/var/lib/sealos/data/default/etc/kubeadm-init.yaml --skip-certificate-key-print --skip-token-print -v 0 --ignore-preflight-errors=SystemVerification) on host(192.168.52.11:22): output(W0901 20:53:05.320846    1982 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/run/containerd/containerd.sock". Please update your configuration!
[init] Using Kubernetes version: v1.24.0
[preflight] Running pre-flight checks
	[WARNING FileExisting-socat]: socat not found in system path
	[WARNING Hostname]: hostname "master1" could not be reached
	[WARNING Hostname]: hostname "master1": lookup master1 on 202.102.227.68: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 k8s.gcr.io/kube-apiserver:v1.24.0: output: E0901 20:55:41.281730    2232 remote_image.go:218] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"k8s.gcr.io/kube-apiserver:v1.24.0\": failed to resolve reference \"k8s.gcr.io/kube-apiserver:v1.24.0\": failed to do request: Head \"https://k8s.gcr.io/v2/kube-apiserver/manifests/v1.24.0\": dial tcp 64.233.188.82:443: i/o timeout" image="k8s.gcr.io/kube-apiserver:v1.24.0"
time="2022-09-01T20:55:41+08:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"k8s.gcr.io/kube-apiserver:v1.24.0\": failed to resolve reference \"k8s.gcr.io/kube-apiserver:v1.24.0\": failed to do request: Head \"https://k8s.gcr.io/v2/kube-apiserver/manifests/v1.24.0\": dial tcp 64.233.188.82:443: i/o timeout"
, error: exit status 1
	[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-controller-manager:v1.24.0: output: E0901 20:58:12.326990    2467 remote_image.go:218] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"k8s.gcr.io/kube-controller-manager:v1.24.0\": failed to resolve reference \"k8s.gcr.io/kube-controller-manager:v1.24.0\": failed to do request: Head \"https://k8s.gcr.io/v2/kube-controller-manager/manifests/v1.24.0\": dial tcp 74.125.203.82:443: i/o timeout" image="k8s.gcr.io/kube-controller-manager:v1.24.0"
time="2022-09-01T20:58:12+08:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"k8s.gcr.io/kube-controller-manager:v1.24.0\": failed to resolve reference \"k8s.gcr.io/kube-controller-manager:v1.24.0\": failed to do request: Head \"https://k8s.gcr.io/v2/kube-controller-manager/manifests/v1.24.0\": dial tcp 74.125.203.82:443: i/o timeout"
, error: exit status 1
	[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-scheduler:v1.24.0: output: E0901 21:00:50.531273    2669 remote_image.go:218] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"k8s.gcr.io/kube-scheduler:v1.24.0\": failed to resolve reference \"k8s.gcr.io/kube-scheduler:v1.24.0\": failed to do request: Head \"https://k8s.gcr.io/v2/kube-scheduler/manifests/v1.24.0\": dial tcp 64.233.188.82:443: i/o timeout" image="k8s.gcr.io/kube-scheduler:v1.24.0"
time="2022-09-01T21:00:50+08:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"k8s.gcr.io/kube-scheduler:v1.24.0\": failed to resolve reference \"k8s.gcr.io/kube-scheduler:v1.24.0\": failed to do request: Head \"https://k8s.gcr.io/v2/kube-scheduler/manifests/v1.24.0\": dial tcp 64.233.188.82:443: i/o timeout"
, error: exit status 1
	[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-proxy:v1.24.0: output: E0901 21:03:20.975709    2877 remote_image.go:218] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"k8s.gcr.io/kube-proxy:v1.24.0\": failed to resolve reference \"k8s.gcr.io/kube-proxy:v1.24.0\": failed to do request: Head \"https://k8s.gcr.io/v2/kube-proxy/manifests/v1.24.0\": dial tcp 74.125.204.82:443: i/o timeout" image="k8s.gcr.io/kube-proxy:v1.24.0"
time="2022-09-01T21:03:20+08:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"k8s.gcr.io/kube-proxy:v1.24.0\": failed to resolve reference \"k8s.gcr.io/kube-proxy:v1.24.0\": failed to do request: Head \"https://k8s.gcr.io/v2/kube-proxy/manifests/v1.24.0\": dial tcp 74.125.204.82:443: i/o timeout"
, error: exit status 1
	[ERROR ImagePull]: failed to pull image k8s.gcr.io/pause:3.7: output: E0901 21:06:02.701290    3080 remote_image.go:218] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"k8s.gcr.io/pause:3.7\": failed to resolve reference \"k8s.gcr.io/pause:3.7\": failed to do request: Head \"https://k8s.gcr.io/v2/pause/manifests/3.7\": dial tcp 108.177.125.82:443: i/o timeout" image="k8s.gcr.io/pause:3.7"
time="2022-09-01T21:06:02+08:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"k8s.gcr.io/pause:3.7\": failed to resolve reference \"k8s.gcr.io/pause:3.7\": failed to do request: Head \"https://k8s.gcr.io/v2/pause/manifests/3.7\": dial tcp 108.177.125.82:443: i/o timeout"
, error: exit status 1
	[ERROR ImagePull]: failed to pull image k8s.gcr.io/etcd:3.5.3-0: output: E0901 21:08:34.131704    3278 remote_image.go:218] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"k8s.gcr.io/etcd:3.5.3-0\": failed to resolve reference \"k8s.gcr.io/etcd:3.5.3-0\": failed to do request: Head \"https://k8s.gcr.io/v2/etcd/manifests/3.5.3-0\": dial tcp 108.177.125.82:443: i/o timeout" image="k8s.gcr.io/etcd:3.5.3-0"
time="2022-09-01T21:08:34+08:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"k8s.gcr.io/etcd:3.5.3-0\": failed to resolve reference \"k8s.gcr.io/etcd:3.5.3-0\": failed to do request: Head \"https://k8s.gcr.io/v2/etcd/manifests/3.5.3-0\": dial tcp 108.177.125.82:443: i/o timeout"
, error: exit status 1
	[ERROR ImagePull]: failed to pull image k8s.gcr.io/coredns/coredns:v1.8.6: output: E0901 21:11:05.483064    3469 remote_image.go:218] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"k8s.gcr.io/coredns/coredns:v1.8.6\": failed to resolve reference \"k8s.gcr.io/coredns/coredns:v1.8.6\": failed to do request: Head \"https://k8s.gcr.io/v2/coredns/coredns/manifests/v1.8.6\": dial tcp 64.233.189.82:443: i/o timeout" image="k8s.gcr.io/coredns/coredns:v1.8.6"
time="2022-09-01T21:11:05+08:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"k8s.gcr.io/coredns/coredns:v1.8.6\": failed to resolve reference \"k8s.gcr.io/coredns/coredns:v1.8.6\": failed to do request: Head \"https://k8s.gcr.io/v2/coredns/coredns/manifests/v1.8.6\": dial tcp 64.233.189.82:443: i/o timeout"
, 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), error(Process exited with status 1). Please clean and reinstall

Clusterfile

apiVersion: apps.sealos.io/v1beta1
kind: Cluster
metadata:
  name: default
spec:
  hosts:
    - ips:
        - 192.168.52.11:22
      roles:
        - master
        - amd64
    - ips:
        - 192.168.52.21:22
        - 192.168.52.22:22
        - 192.168.52.23:22
        - 192.168.52.24:22
        - 192.168.52.25:22
        - 192.168.52.26:22
      roles:
        - node
        - amd64
  image:
    - labring/kubernetes:v1.24.0
    - labring/calico:v3.22.1
    - labring/openebs:v1.9.0
  ssh:
    passwd: 123456
    port: 22
    user: root

[cuisongliu]

crictl config is ?? image-cri-shim status is ?

[itxiao6]

kubeadm config images pull 不行
kubeadm config images pull --image-repository registry.cn-hangzhou.aliyuncs.com/google_containers 可以
是否可以 在kubeadm init 的时候加入 --image-repository registry.cn-hangzhou.aliyuncs.com/google_containers 来解决呢
/var/lib/sealos/data/default/etc/kubeadm-init.yaml 每次安装都会被覆盖 这里面的内容怎么自定义呢

[cuisongliu]

kubeadm config images pull 不行
kubeadm config images pull --image-repository registry.cn-hangzhou.aliyuncs.com/google_containers 可以
是否可以 在kubeadm init 的时候加入 --image-repository registry.cn-hangzhou.aliyuncs.com/google_containers 来解决呢
/var/lib/sealos/data/default/etc/kubeadm-init.yaml 每次安装都会被覆盖 这里面的内容怎么自定义呢

不需要的 有私有仓库会自己去私有仓库拉取。看一下image-cri-shim 理论会自动下载的。

[cuisongliu]

root@docker-test4:~# crictl images
IMAGE                                                            TAG                 IMAGE ID            SIZE
sealos.hub:5000/coredns/coredns                                  v1.9.3              b19406328e70d       13.4MB
sealos.hub:5000/etcd                                             3.5.4-0             8e041a3b0ba8b       81.1MB
sealos.hub:5000/kube-apiserver                                   v1.25.0             4a10a2c929d54       31.2MB
sealos.hub:5000/kube-controller-manager                          v1.25.0             35cb04d93081d       28.4MB
sealos.hub:5000/kube-proxy                                       v1.25.0             f5e24e0ab5f8d       18.1MB
sealos.hub:5000/kube-scheduler                                   v1.25.0             b933d73979ff4       14.3MB
sealos.hub:5000/labring/docker-cni-plugins                       v1.1.1              aba0e1b9a4f65       35.3MB
sealos.hub:5000/pause                                            3.8                 4e42fb3c9d90e       268kB
sealos.hub:5000/rancher/mirrored-flannelcni-flannel-cni-plugin   v1.1.0              b04a1a4152e14       3.64MB
sealos.hub:5000/rancher/mirrored-flannelcni-flannel              v0.19.0             63a558e36e685       20.5MB

[itxiao6]

按照这样 我推送到 私有仓库里

docker pull registry.k8s.io/kube-apiserver:v1.25.0
docker tag registry.k8s.io/kube-apiserver:v1.25.0 harbor.huoxingqianli.com/k8s.gcr.io/kube-apiserver:v1.25.0
docker push harbor.huoxingqianli.com/k8s.gcr.io/kube-apiserver:v1.25.0


docker pull registry.k8s.io/kube-controller-manager:v1.25.0
docker tag registry.k8s.io/kube-controller-manager:v1.25.0 harbor.huoxingqianli.com/k8s.gcr.io/kube-controller-manager:v1.25.0
docker push harbor.huoxingqianli.com/k8s.gcr.io/kube-controller-manager:v1.25.0



docker pull registry.k8s.io/kube-scheduler:v1.25.0
docker tag registry.k8s.io/kube-scheduler:v1.25.0 harbor.huoxingqianli.com/k8s.gcr.io/kube-scheduler:v1.25.0
docker push harbor.huoxingqianli.com/k8s.gcr.io/kube-scheduler:v1.25.0


docker pull registry.k8s.io/kube-proxy:v1.25.0
docker tag registry.k8s.io/kube-proxy:v1.25.0 harbor.huoxingqianli.com/k8s.gcr.io/kube-proxy:v1.25.0
docker push harbor.huoxingqianli.com/k8s.gcr.io/kube-proxy:v1.25.0


docker pull registry.k8s.io/pause:3.8
docker tag registry.k8s.io/pause:3.8 harbor.huoxingqianli.com/k8s.gcr.io/pause:3.8
docker push harbor.huoxingqianli.com/k8s.gcr.io/pause:3.8

docker pull registry.k8s.io/etcd:3.5.4-0
docker tag registry.k8s.io/etcd:3.5.4-0 harbor.huoxingqianli.com/k8s.gcr.io/etcd:3.5.4-0
docker push harbor.huoxingqianli.com/k8s.gcr.io/etcd:3.5.4-0


docker pull registry.k8s.io/coredns/coredns:v1.9.3
docker tag registry.k8s.io/coredns:v1.9.3 harbor.huoxingqianli.com/k8s.gcr.io/coredns:v1.9.3
docker push harbor.huoxingqianli.com/k8s.gcr.io/coredns:v1.9.3

然后在 每个节点 拉取一遍

拉取完 还需要 给这些镜像 新增一个tag 吧

[itxiao6]

拉取镜像的时候 需要指定 命名空间

ctr -n k8s.io image pull harbor.huoxingqianli.com/k8s.gcr.io/kube-apiserver:v1.24.0 
ctr -n k8s.io image tag harbor.huoxingqianli.com/k8s.gcr.io/kube-apiserver:v1.24.0 k8s.gcr.io/kube-apiserver:v1.24.0 

ctr -n k8s.io image pull harbor.huoxingqianli.com/k8s.gcr.io/kube-controller-manager:v1.24.0 
ctr -n k8s.io image tag harbor.huoxingqianli.com/k8s.gcr.io/kube-controller-manager:v1.24.0 k8s.gcr.io/kube-controller-manager:v1.24.0 

ctr -n k8s.io image pull harbor.huoxingqianli.com/k8s.gcr.io/kube-scheduler:v1.24.0 
ctr -n k8s.io image tag harbor.huoxingqianli.com/k8s.gcr.io/kube-scheduler:v1.24.0 k8s.gcr.io/kube-scheduler:v1.24.0 

ctr -n k8s.io image pull harbor.huoxingqianli.com/k8s.gcr.io/kube-proxy:v1.24.0 
ctr -n k8s.io image tag harbor.huoxingqianli.com/k8s.gcr.io/kube-proxy:v1.24.0 k8s.gcr.io/kube-proxy:v1.24.0 

ctr -n k8s.io image pull harbor.huoxingqianli.com/k8s.gcr.io/pause:3.7 
ctr -n k8s.io image tag harbor.huoxingqianli.com/k8s.gcr.io/pause:3.7 k8s.gcr.io/pause:3.7 

ctr -n k8s.io image pull harbor.huoxingqianli.com/k8s.gcr.io/etcd:3.5.3-0 
ctr -n k8s.io image tag harbor.huoxingqianli.com/k8s.gcr.io/etcd:3.5.3-0 k8s.gcr.io/etcd:3.5.3-0 

ctr -n k8s.io image pull harbor.huoxingqianli.com/k8s.gcr.io/coredns:v1.8.6 
ctr -n k8s.io image tag harbor.huoxingqianli.com/k8s.gcr.io/coredns:v1.8.6 k8s.gcr.io/coredns/coredns:v1.8.6 

[itxiao6]

root@docker-test4:~# crictl images
IMAGE                                                            TAG                 IMAGE ID            SIZE
sealos.hub:5000/coredns/coredns                                  v1.9.3              b19406328e70d       13.4MB
sealos.hub:5000/etcd                                             3.5.4-0             8e041a3b0ba8b       81.1MB
sealos.hub:5000/kube-apiserver                                   v1.25.0             4a10a2c929d54       31.2MB
sealos.hub:5000/kube-controller-manager                          v1.25.0             35cb04d93081d       28.4MB
sealos.hub:5000/kube-proxy                                       v1.25.0             f5e24e0ab5f8d       18.1MB
sealos.hub:5000/kube-scheduler                                   v1.25.0             b933d73979ff4       14.3MB
sealos.hub:5000/labring/docker-cni-plugins                       v1.1.1              aba0e1b9a4f65       35.3MB
sealos.hub:5000/pause                                            3.8                 4e42fb3c9d90e       268kB
sealos.hub:5000/rancher/mirrored-flannelcni-flannel-cni-plugin   v1.1.0              b04a1a4152e14       3.64MB
sealos.hub:5000/rancher/mirrored-flannelcni-flannel              v0.19.0             63a558e36e685       20.5MB

这时候有个问题，这样操作完 我sealos reset 后 各个节点的镜像又被删掉了 。
sealos apply -f Clusterfile 的时候 又没有这些镜像了

[cuisongliu]

root@docker-test4:~# crictl images
IMAGE TAG IMAGE ID SIZE
sealos.hub:5000/coredns/coredns v1.9.3 b19406328e70d 13.4MB
sealos.hub:5000/etcd 3.5.4-0 8e041a3b0ba8b 81.1MB
sealos.hub:5000/kube-apiserver v1.25.0 4a10a2c929d54 31.2MB
sealos.hub:5000/kube-controller-manager v1.25.0 35cb04d93081d 28.4MB
sealos.hub:5000/kube-proxy v1.25.0 f5e24e0ab5f8d 18.1MB
sealos.hub:5000/kube-scheduler v1.25.0 b933d73979ff4 14.3MB
sealos.hub:5000/labring/docker-cni-plugins v1.1.1 aba0e1b9a4f65 35.3MB
sealos.hub:5000/pause 3.8 4e42fb3c9d90e 268kB
sealos.hub:5000/rancher/mirrored-flannelcni-flannel-cni-plugin v1.1.0 b04a1a4152e14 3.64MB
sealos.hub:5000/rancher/mirrored-flannelcni-flannel v0.19.0 63a558e36e685 20.5MB

这个的意思是让你执行一下crictl images 是不是sealos.hub开头的。。。。不是tag镜像。systemctl status image-cri-shim 一下

[itxiao6]

image-cri-shim 的状态

[root@master1 ~]# systemctl status image-cri-shim
● image-cri-shim.service - image-cri-shim
   Loaded: loaded (/etc/systemd/system/image-cri-shim.service; enabled; vendor preset: disabled)
   Active: active (running) since 五 2022-09-02 14:18:20 CST; 1h 32min ago
 Main PID: 14049 (image-cri-shim)
    Tasks: 10
   Memory: 33.6M
   CGroup: /system.slice/image-cri-shim.service
           └─14049 /usr/bin/image-cri-shim -f /etc/image-cri-shim.yaml

9月 02 15:50:35 master1 image-cri-shim[14049]: 2022-09-02T15:50:35 info image kube-apiserver:v1.25.0 not found in registry, skipping
9月 02 15:50:35 master1 image-cri-shim[14049]: 2022-09-02T15:50:35 info begin image: registry.k8s.io/kube-apiserver:v1.25.0, after image: registry.k8s.io...ageStatus
9月 02 15:50:35 master1 image-cri-shim[14049]: 2022-09-02T15:50:35 info cmd for bash in host: crictl images -q
9月 02 15:50:35 master1 image-cri-shim[14049]: 2022-09-02T15:50:35 info domain: registry.k8s.io, imageName: kube-apiserver:v1.25.0, action: PullImage
9月 02 15:50:35 master1 image-cri-shim[14049]: 2022-09-02T15:50:35 info address: http://sealos.hub:5000, base64: YWRtaW46cGFzc3cwcmQ=, imageName: kube-apiserver
9月 02 15:50:35 master1 image-cri-shim[14049]: 2022-09-02T15:50:35 info pre image name: kube-apiserver, pre image tag: v1.25.0
9月 02 15:50:35 master1 image-cri-shim[14049]: 2022-09-02T15:50:35 info data: Get "http://sealos.hub:5000/v2/kube-apiserver/tags/list": dial tcp: lookup ...such host
9月 02 15:50:35 master1 image-cri-shim[14049]: 2022-09-02T15:50:35 warn convert registry data error
9月 02 15:50:35 master1 image-cri-shim[14049]: 2022-09-02T15:50:35 info image kube-apiserver:v1.25.0 not found in registry, skipping
9月 02 15:50:35 master1 image-cri-shim[14049]: 2022-09-02T15:50:35 info begin image: registry.k8s.io/kube-apiserver:v1.25.0, after image: registry.k8s.io...PullImage
Hint: Some lines were ellipsized, use -l to show in full.

crictl images 是空的 ，目前这里看到的都是我手动拉取的镜像

[root@master1 ~]# crictl images
IMAGE                                                                         TAG                 IMAGE ID            SIZE
harbor.huoxingqianli.com/k8s.gcr.io/coredns                                   v1.9.3              5185b96f0becf       14.8MB
k8s.gcr.io/coredns/coredns                                                    v1.9.3              5185b96f0becf       14.8MB
registry.cn-hangzhou.aliyuncs.com/google_containers/coredns                   v1.9.3              5185b96f0becf       14.8MB
harbor.huoxingqianli.com/k8s.gcr.io/etcd                                      3.5.4-0             a8a176a5d5d69       102MB
k8s.gcr.io/etcd                                                               3.5.4-0             a8a176a5d5d69       102MB
registry.cn-hangzhou.aliyuncs.com/google_containers/etcd                      3.5.4-0             a8a176a5d5d69       102MB
harbor.huoxingqianli.com/k8s.gcr.io/kube-apiserver                            v1.25.0             4d2edfd10d3e3       34.2MB
k8s.gcr.io/kube-apiserver                                                     v1.25.0             4d2edfd10d3e3       34.2MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver            v1.25.0             4d2edfd10d3e3       34.2MB
harbor.huoxingqianli.com/k8s.gcr.io/kube-controller-manager                   v1.25.0             1a54c86c03a67       31.3MB
k8s.gcr.io/kube-controller-manager                                            v1.25.0             1a54c86c03a67       31.3MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager   v1.25.0             1a54c86c03a67       31.3MB
harbor.huoxingqianli.com/k8s.gcr.io/kube-proxy                                v1.25.0             58a9a0c6d96f2       20.3MB
k8s.gcr.io/kube-proxy                                                         v1.25.0             58a9a0c6d96f2       20.3MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy                v1.25.0             58a9a0c6d96f2       20.3MB
harbor.huoxingqianli.com/k8s.gcr.io/kube-scheduler                            v1.25.0             bef2cf3115095       15.8MB
k8s.gcr.io/kube-scheduler                                                     v1.25.0             bef2cf3115095       15.8MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler            v1.25.0             bef2cf3115095       15.8MB
harbor.huoxingqianli.com/k8s.gcr.io/pause                                     3.8                 4873874c08efc       311kB
k8s.gcr.io/pause                                                              3.8                 4873874c08efc       311kB
registry.cn-hangzhou.aliyuncs.com/google_containers/pause                     3.8                 4873874c08efc       311kB
k8s.gcr.io/coredns/coredns                                                    v1.8.6              a4ca41631cc7a       13.6MB
registry.cn-hangzhou.aliyuncs.com/google_containers/coredns                   v1.8.6              a4ca41631cc7a       13.6MB
k8s.gcr.io/etcd                                                               3.5.3-0             aebe758cef4cd       102MB
registry.cn-hangzhou.aliyuncs.com/google_containers/etcd                      3.5.3-0             aebe758cef4cd       102MB
k8s.gcr.io/kube-apiserver                                                     v1.24.0             529072250ccc6       33.8MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver            v1.24.0             529072250ccc6       33.8MB
k8s.gcr.io/kube-controller-manager                                            v1.24.0             88784fb4ac2f6       31MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager   v1.24.0             88784fb4ac2f6       31MB
k8s.gcr.io/kube-proxy                                                         v1.24.0             77b49675beae1       39.5MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy                v1.24.0             77b49675beae1       39.5MB
k8s.gcr.io/kube-scheduler                                                     v1.24.0             e3ed7dee73e93       15.5MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler            v1.24.0             e3ed7dee73e93       15.5MB
k8s.gcr.io/pause                                                              3.7                 221177c6082a8       311kB
registry.cn-hangzhou.aliyuncs.com/google_containers/pause                     3.7                 221177c6082a8       311kB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver            v1.24.4             6cab9d1bed1be       33.8MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager   v1.24.4             1f99cb6da9a82       31MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy                v1.24.4             7a53d1e08ef58       39.5MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler            v1.24.4             03fa22539fc1c       15.5MB

[itxiao6]

在等待过程中

192.168.52.11:22: W0902 14:39:15.332346   21605 initconfiguration.go:119] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/run/containerd/containerd.sock". Please update your configuration!
192.168.52.11:22: [init] Using Kubernetes version: v1.25.0
192.168.52.11:22: [preflight] Running pre-flight checks
192.168.52.11:22: 	[WARNING FileExisting-socat]: socat not found in system path
192.168.52.11:22: 	[WARNING Hostname]: hostname "master1" could not be reached
192.168.52.11:22: 	[WARNING Hostname]: hostname "master1": lookup master1 on 202.102.227.68:53: no such host
192.168.52.11:22: [preflight] Pulling images required for setting up a Kubernetes cluster
192.168.52.11:22: [preflight] This might take a minute or two, depending on the speed of your internet connection
192.168.52.11:22: [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
192.168.52.11:22: error execution phase preflight: [preflight] Some fatal errors occurred:

我在节点上执行了一下 ps 显示

[root@master1 ~]# ps aux | grep "containerd" 正在拉取 registry.k8s.io/kube-scheduler:v1.25.0 
root     13975  0.2  0.9 1256404 77640 ?       Ssl  14:18   0:04 /usr/bin/containerd
root     21506  0.0  0.2 712392 17372 ?        Sl   14:39   0:00 /usr/bin/containerd-shim-runc-v2 -namespace default -id 192e9fa06323b73dd72ccdaa656df33fceda540a1e2cfe565057098954317dab -address /run/containerd/containerd.sock
root     22380  0.0  0.2 732460 23232 pts/1    Sl+  14:46   0:00 /usr/bin/crictl -r unix:///run/containerd/containerd.sock pull registry.k8s.io/kube-scheduler:v1.25.0
root     22422  0.0  0.0 112736  2368 pts/0    S+   14:47   0:00 grep --color=auto containerd

[itxiao6]

您这个 sealos.hub:5000 是没看到的

[itxiao6]

目前遇到的问题就是 新建一个集群的时候 走到kubeadm init 的时候 长时间等待然后，报错的问题。

sealos apply -f Clusterfile

Clusterfile

apiVersion: apps.sealos.io/v1beta1
kind: Cluster
metadata:
  name: default
spec:
  hosts:
    - ips:
        - 192.168.52.11:22
      roles:
        - master
        - amd64
    - ips:
        - 192.168.52.21:22
        - 192.168.52.22:22
        - 192.168.52.23:22
        - 192.168.52.24:22
        - 192.168.52.25:22
        - 192.168.52.26:22
      roles:
        - node
        - amd64
  image:
    - labring/kubernetes:v1.25.0
    - labring/calico:v3.22.1
    - labring/openebs:v1.9.0
  ssh:
    passwd: 123456
    port: 22
    user: root

系统是Centos7 内核:5.19.6-1.el7.elrepo.x86_64

[cuisongliu]

/etc/hosts 没有sealos.hub的域名？？？？

[itxiao6]

没有 ，原因可能是 我执行sealos 没有在节点上执行。而是在另外一台机器上执行的