基础环境需要哪些，ansible，docker？ 望在文档中标识一下

请问一下安装了一个多小时提示这个报错是哪里配置错了？新机器，环境干净，前面uninstall过两次

FAILED - RETRYING: kubeadm | Initialize first master (3 retries left).
FAILED - RETRYING: kubeadm | Initialize first master (2 retries left).
FAILED - RETRYING: kubeadm | Initialize first master (1 retries left).
fatal: [master1]: FAILED! => {
“attempts”: 3,
“changed”: true,
“cmd”: [
“timeout”,
“-k”,
“300s”,
“300s”,
“/usr/local/bin/kubeadm”,
“init”,
“–config=/etc/kubernetes/kubeadm-config.yaml”,
“–ignore-preflight-errors=all”,
“–skip-phases=addon/coredns”,
“–upload-certs”
],
“delta”: “0:05:00.037168″,
“end”: “2020-08-07 14:50:01.396185”,
“failed_when_result”: true,
“rc”: 124,
“start”: “2020-08-07 14:45:01.359017”
}

STDOUT:

[init] Using Kubernetes version: v1.16.7
[preflight] Running pre-flight checks
[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’
[kubelet-start] Writing kubelet environment file with flags to file “/var/lib/kubelet/kubeadm-flags.env”
[kubelet-start] Writing kubelet configuration to file “/var/lib/kubelet/config.yaml”
[kubelet-start] Activating the kubelet service
[certs] Using certificateDir folder “/etc/kubernetes/ssl”
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] External etcd mode: Skipping etcd/ca certificate authority generation
[certs] External etcd mode: Skipping etcd/server certificate generation
[certs] External etcd mode: Skipping etcd/peer certificate generation
[certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation
[certs] External etcd mode: Skipping apiserver-etcd-client certificate generation
[certs] Using the existing “sa” key
[kubeconfig] Using kubeconfig folder “/etc/kubernetes”
[kubeconfig] Using existing kubeconfig file: “/etc/kubernetes/admin.conf”
[kubeconfig] Using existing kubeconfig file: “/etc/kubernetes/kubelet.conf”
[kubeconfig] Using existing kubeconfig file: “/etc/kubernetes/controller-manager.conf”
[kubeconfig] Using existing kubeconfig file: “/etc/kubernetes/scheduler.conf”
[control-plane] Using manifest folder “/etc/kubernetes/manifests”
[control-plane] Creating static Pod manifest for “kube-apiserver”
[controlplane] Adding extra host path mount “etc-pki-tls” to “kube-apiserver”
[controlplane] Adding extra host path mount “etc-pki-ca-trust” to “kube-apiserver”
[control-plane] Creating static Pod manifest for “kube-controller-manager”
[controlplane] Adding extra host path mount “etc-pki-tls” to “kube-apiserver”
[controlplane] Adding extra host path mount “etc-pki-ca-trust” to “kube-apiserver”
[control-plane] Creating static Pod manifest for “kube-scheduler”
[controlplane] Adding extra host path mount “etc-pki-tls” to “kube-apiserver”
[controlplane] Adding extra host path mount “etc-pki-ca-trust” to “kube-apiserver”
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory “/etc/kubernetes/manifests”. This can take up to 5m0s
[kubelet-check] Initial timeout of 40s passed.

STDERR:

[WARNING Port-6443]: Port 6443 is in use
[WARNING Port-10251]: Port 10251 is in use
[WARNING Port-10252]: Port 10252 is in use
[WARNING FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists
[WARNING FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists
[WARNING FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists
[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
[WARNING Port-10250]: Port 10250 is in use

MSG:

non-zero return code

NO MORE HOSTS LEFT *******************************************************************************************************

PLAY RECAP ***************************************************************************************************************
localhost : ok=1 changed=0 unreachable=0 failed=0

master1 : ok=417 changed=76 unreachable=0 failed=1

master2 : ok=406 changed=78 unreachable=0 failed=0

master3 : ok=406 changed=78 unreachable=0 failed=0

node1 : ok=330 changed=61 unreachable=0 failed=0

Friday 07 August 2020 14:50:01 +0800 (0:20:16.326) 0:30:25.065 *********

kubernetes/master : kubeadm | Initialize first master ———————————————————- 1216.33s
container-engine/docker : ensure docker packages are installed ————————————————— 36.87s
kubernetes/preinstall : Install packages requirements ———————————————————— 26.10s
etcd : Gen_certs | Write etcd master certs ———————————————————————– 23.58s
container-engine/docker : Docker | reload docker —————————————————————– 15.88s
bootstrap-os : Install libselinux python package —————————————————————— 8.91s
etcd : Gen_certs | Gather etcd master certs ———————————————————————– 6.01s
etcd : Configure | Check if etcd cluster is healthy ————————————————————— 4.87s
etcd : Install | Copy etcdctl binary from docker container ——————————————————– 4.78s
download : download | Download files / images ——————————————————————— 4.45s
download : download_file | Download item ————————————————————————– 4.26s
download : download_file | Download item ————————————————————————– 4.09s
etcd : wait for etcd up ——————————————————————————————- 3.50s
etcd : reload etcd ———————————————————————————————— 3.20s
kubernetes/node : install | Copy kubelet binary from download dir ————————————————- 3.13s
download : download | Sync files / images from ansible host to nodes ———————————————- 3.08s
etcd : Gen_certs | run cert generation script ——————————————————————— 2.77s
download : download_file | Download item ————————————————————————– 2.62s
chrony : start chrony server ————————————————————————————– 2.47s
container-engine/docker : ensure service is started if docker packages are already present ———————— 2.45s
failed!

please refer to https://kubesphere.io/docs/v2.1/zh-CN/faq/faq-install/

TASK [kubernetes/master : kubeadm | Initialize first master] *************************************************************
Friday 07 August 2020 15:18:06 +0800 (0:00:00.461) 0:08:36.763 *********
skipping: [master2]
skipping: [master3]
就是在初始化master1的时候报的错

离线安装报这个错误，麻烦帮忙看下什么问题？

DukeChiang 请问这个问题解决了吗？我也遇到这个问题了，报的同样的错

fnag_huna
看样子是pip源的问题
如果没有用glusterfs的话，可以在kubesphere/roles/prepare/nodes/tasks/main.yaml中注释掉glusterfs相关的任务。

v3.0.0已发布，可以试试

Cauchy 感谢回复！但尝试注释以后得到了同样的结果。
umount: /kubeinstaller/yum_repo/iso: mountpoint not found这行提示是否提示我未将镜像文件放到yum_repo中呢？

fnag_huna

这个只是说明umount的时候没有对应的挂载点。
还是那个pip | Installing pip报错吗？注释掉的话应该就不会执行那个task了呀。

Cauchy 我没有找到您说的这一行在哪里，我的报错信息一直是这样的

Cauchy 是CentOS Linux release 7.8.2003 (Core)

Cauchy 好的，谢谢！

fnag_huna
可以执行docker info看下docker的配置，是不是这个本地仓库的地址没有加到docker的insecure_registries中。

Cauchy 看了一下，里面是有本地仓库地址的：Insecure Registries: 192.168.2.32:5000 127.0.0.0/8这是什么原因呢

fnag_huna
先docker ps | grep registry检查下这个仓库服务是否正常，然后push个镜像试下是否能成功。

Cauchy 顺带一提，我现在安装的是 all-in-one 单节点模式的，之前尝试安装多节点时出现了这样的情况
我的hosts.ini配置是这样的：
请问是哪里出问题了？

Cauchy push了一个镜像，果然无法成功，一直在retrying