离线安装 KubeSphere 2.1.1 与 Kubernetes

wcsemail

我太难了，在线、离线都安装，都装不上，装了卸，卸了装。防火墙也关了
TASK [kubernetes/preinstall : Install packages requirements] ***********************************************************************************************************************************************************
Sunday 26 April 2020 20:17:45 +0800 (0:00:00.161) 0:00:40.420 **********
FAILED - RETRYING: Install packages requirements (4 retries left).
ok: [master]
FAILED - RETRYING: Install packages requirements (4 retries left).
FAILED - RETRYING: Install packages requirements (3 retries left).
FAILED - RETRYING: Install packages requirements (3 retries left).
FAILED - RETRYING: Install packages requirements (2 retries left).
FAILED - RETRYING: Install packages requirements (2 retries left).
FAILED - RETRYING: Install packages requirements (1 retries left).
FAILED - RETRYING: Install packages requirements (1 retries left).
fatal: [node2]: FAILED! => {
“attempts”: 4,
“changed”: false,
“rc”: 1,
“results”: []
}

MSG:

http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
正在尝试其它镜像。
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
正在尝试其它镜像。
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
正在尝试其它镜像。
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
正在尝试其它镜像。
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
正在尝试其它镜像。
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
正在尝试其它镜像。
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
正在尝试其它镜像。
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
正在尝试其它镜像。
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
正在尝试其它镜像。
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
正在尝试其它镜像。

One of the configured repositories failed (centos7),
and yum doesn’t have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work “fix” this:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
        yum --disablerepo=bash ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
    will then just ignore the repository until you permanently enable it
    again or use --enablerepo for temporary usage:

        yum-config-manager --disable bash
    or
        subscription-manager repos --disable=bash

 5. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

        yum-config-manager --save --setopt=bash.skip_if_unavailable=true

failure: repodata/repomd.xml from bash: [Errno 256] No more mirrors to try.
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”
http://192.168.4.99:5080/yum_repo/iso/repodata/repomd.xml: [Errno 14] curl#7 - “Failed connect to 192.168.4.99:5080; 拒绝连接”

fatal: [node1]: FAILED! => {
“attempts”: 4,
“changed”: false,
“rc”: 1,
“results”: []
}

MSG:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
        yum --disablerepo=bash ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
    will then just ignore the repository until you permanently enable it
    again or use --enablerepo for temporary usage:

        yum-config-manager --disable bash
    or
        subscription-manager repos --disable=bash

 5. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

        yum-config-manager --save --setopt=bash.skip_if_unavailable=true

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

Forest-L

wcsemail
yum源有问题，请参考论坛该文章，https://kubesphere.com.cn/forum/d/929-yum

qcloud

wcsemail 我也是遇到各种奇怪的问题

jinwen

wcsemail 我后来的解决方法是删除了/etc/docker/deamon.json文件，因为总是一直报docker不对，把这个文件改了又改，后来删除以后成功安装

wcsemail

Forest-L 好的，我试试，谢谢

rayzhou2017

Forest-L @Feynman 帮忙确认一下文档问题

ussiwfm

wcsemail 我安装成功了，他们关于离线安装文档中没有加入两个前提，关闭防火墙和提前安装两个组件
yum install sshpass
yum install docker-ce docker-ce-cli -y 请了解，做完没安装成功就是没有安装文档严格操作，多了不必要的东西

Forest-L

ussiwfm 是的，严格按照文档要求来一般都会成功的；防火墙最好关掉(不清楚的请搜索对应机器类型centos、ubuntu等怎么关防火墙)；sshpass和docker两个组件都会在脚本中安装，不需要提前安装。

Feynman

ussiwfm 多谢提醒，在本帖开头的前提条件中是有说明关闭防火墙的，两个组件离线安装包会自动安装

wcsemail

失败，失败了一个星期了，各种失败
ASK [kubernetes/preinstall : Update common_required_pkgs with ipvsadm when kube_proxy_mode is ipvs] *************************************************************************************************************************************
Monday 27 April 2020 13:05:31 +0800 (0:00:00.114) 0:00:42.395 **********
ok: [node1]
ok: [master]
ok: [node2]

TASK [kubernetes/preinstall : Install packages requirements] *****************************************************************************************************************************************************************************
Monday 27 April 2020 13:05:31 +0800 (0:00:00.185) 0:00:42.580 **********
FAILED - RETRYING: Install packages requirements (4 retries left).
FAILED - RETRYING: Install packages requirements (4 retries left).
ok: [master]
FAILED - RETRYING: Install packages requirements (3 retries left).
FAILED - RETRYING: Install packages requirements (3 retries left).
FAILED - RETRYING: Install packages requirements (2 retries left).
FAILED - RETRYING: Install packages requirements (1 retries left).
FAILED - RETRYING: Install packages requirements (2 retries left).
fatal: [node2]: FAILED! => {
“attempts”: 4,
“changed”: false,
“rc”: 1,
“results”: []
}

MSG:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
        yum --disablerepo=bash ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
    will then just ignore the repository until you permanently enable it
    again or use --enablerepo for temporary usage:

        yum-config-manager --disable bash
    or
        subscription-manager repos --disable=bash

 5. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

        yum-config-manager --save --setopt=bash.skip_if_unavailable=true

FAILED - RETRYING: Install packages requirements (1 retries left).
fatal: [node1]: FAILED! => {
“attempts”: 4,
“changed”: false,
“rc”: 1,
“results”: []
}

MSG:

rayzhou2017

wcsemail 你这个看起来还是yum源的问题，你没参考https://kubesphere.com.cn/forum/d/929-yum？

wcsemail

参考了，法子都用了，机器都格式化三次了

wcsemail

各位大佬，搞不定呀
TASK [download : download_container | Download image if required ( 192.168.4.99:5000/mirrorgooglecontainers/pause-amd64:3.1 )] ***********************************************************************************************************
Tuesday 28 April 2020 11:18:13 +0800 (0:00:00.153) 0:01:50.854 *********
FAILED - RETRYING: download_container | Download image if required ( 192.168.4.99:5000/mirrorgooglecontainers/pause-amd64:3.1 ) (4 retries left).
FAILED - RETRYING: download_container | Download image if required ( 192.168.4.99:5000/mirrorgooglecontainers/pause-amd64:3.1 ) (4 retries left).
FAILED - RETRYING: download_container | Download image if required ( 192.168.4.99:5000/mirrorgooglecontainers/pause-amd64:3.1 ) (4 retries left).
FAILED - RETRYING: download_container | Download image if required ( 192.168.4.99:5000/mirrorgooglecontainers/pause-amd64:3.1 ) (3 retries left).
FAILED - RETRYING: download_container | Download image if required ( 192.168.4.99:5000/mirrorgooglecontainers/pause-amd64:3.1 ) (3 retries left).
FAILED - RETRYING: download_container | Download image if required ( 192.168.4.99:5000/mirrorgooglecontainers/pause-amd64:3.1 ) (2 retries left).
FAILED - RETRYING: download_container | Download image if required ( 192.168.4.99:5000/mirrorgooglecontainers/pause-amd64:3.1 ) (3 retries left).
FAILED - RETRYING: download_container | Download image if required ( 192.168.4.99:5000/mirrorgooglecontainers/pause-amd64:3.1 ) (2 retries left).
FAILED - RETRYING: download_container | Download image if required ( 192.168.4.99:5000/mirrorgooglecontainers/pause-amd64:3.1 ) (1 retries left).
FAILED - RETRYING: download_container | Download image if required ( 192.168.4.99:5000/mirrorgooglecontainers/pause-amd64:3.1 ) (1 retries left).
fatal: [master -> master]: FAILED! => {
“attempts”: 4,
“changed”: true,
“cmd”: [
“/usr/bin/docker”,
“pull”,
“192.168.4.99:5000/mirrorgooglecontainers/pause-amd64:3.1″
],
“delta”: “0:00:00.068527″,
“end”: “2020-04-28 11:18:26.854654”,
“rc”: 1,
“start”: “2020-04-28 11:18:26.786127″
}

STDERR:

Error response from daemon: Get http://192.168.4.99:5000/v2/: dial tcp 192.168.4.99:5000: connect: connection refused

MSG:

non-zero return code

FAILED - RETRYING: download_container | Download image if required ( 192.168.4.99:5000/mirrorgooglecontainers/pause-amd64:3.1 ) (2 retries left).
fatal: [node1 -> master]: FAILED! => {
“attempts”: 4,
“changed”: true,
“cmd”: [
“/usr/bin/docker”,
“pull”,
“192.168.4.99:5000/mirrorgooglecontainers/pause-amd64:3.1”
],
“delta”: “0:00:00.075878″,
“end”: “2020-04-28 11:18:30.915696”,
“rc”: 1,
“start”: “2020-04-28 11:18:30.839818″
}

STDERR:

Error response from daemon: Get http://192.168.4.99:5000/v2/: dial tcp 192.168.4.99:5000: connect: connection refused

MSG:

non-zero return code

FAILED - RETRYING: download_container | Downl

a01871000

wcsemail 我也是有什麼解決方法嗎??

wcsemail

终于解决，centos最小安装/ 目录默认50g肯定不行，加到100g就可以了

jinwen

wcsemail 请问下具体如何更改？

Student-party

[root@k8s-master kubesphere]# kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath=‘{.items[0].metadata.name}’) -f
Error from server (BadRequest): container “installer” in pod “ks-installer-59fb465b7-pzvv2” is waiting to start: ContainerCreating

环境： k8s1.15版本
在安装KubeSphere完整版的时候，查看安装日志的报错
查看了一下pod，也是出于 ContainerCreating状态

Student-party

Student-party 已处理此问题是无法拉去镜像，但是我提前下载了docker 镜像后，也重新配置了images只拉去本地，pod状态已是run，但是查看了安装logs，一直报
FAILED - RETRYING: Metrics-Server | Waitting for v1beta1.metrics.k8s.io ready (43 retries left)

Cauchy

Student-party
v1beta1.metrics.k8s.io这个是由于集群中的metrics-server不正常导致的哦，可以检查下及群里的metrics-server
可以看看kube-system下的pod状态
可以通过kubectl get apiservices查看相关api状态

Student-party

Cauchy 鼓捣好了，但访问的时候报英特网无效连接错误，懵了。想卸载了重装有没有卸载脚本？

jinchen

请问，我现在想使用在线安装脚本或者离线安装脚本，使用我本地私有harbor仓库，但是更改common配置没有生效，想问该如何设置呢？另外harbor是否需要https协议

Feynman

jinchen 那样会麻烦一些，你需要把所有镜像提前推送到 harbor 镜像仓库，然后在安装脚本里改镜像地址。为什么不直接用打包好的离线 installer 安装呢？

jinchen

Feynman 那就是了，在研究这个能不能在线安装使用本地局域网的harbor做加速，所以遇到了这个问题了