sealos
sealos copied to clipboard
BUG: 自定义安装目录,集群部署卡死
版本:4.1.3 问题:不自定义容器目录,不会出现该问题
- 命令:
sealos run --cluster-root=/data/sealos/ --env criData=/data/cri/lib/containerd --env registryData=/data/cri/lib/registry labring/kubernetes:v1.24.0 labring/calico:v3.22.1 \
--masters 192.168.0.10,192.168.0.4 \
--nodes 192.168.0.8,192.168.0.2,192.168.0.5 --pk /data/install/p.pem
- 执行过程:
[root@apps-master1 scripts]# sealos run --cluster-root=/data/sealos/ --env criData=/data/cri/lib/containerd --env registryData=/data/cri/lib/registry labring/kubernetes:v1.24.0 labring/calico:v3.22.1 \
> --single
2022-09-08T11:44:42 info Start to create a new cluster: master [192.168.0.10], worker []
2022-09-08T11:44:42 info Executing pipeline Check in CreateProcessor.
2022-09-08T11:44:42 info checker:hostname [192.168.0.10:22]
2022-09-08T11:44:42 info checker:timeSync [192.168.0.10:22]
2022-09-08T11:44:42 info Executing pipeline PreProcess in CreateProcessor.
49cdd4d1a0d840fae1ffd193983701f9f128c0ee50408fd125d1555b67e4f55b
29516dc98b4b2d4fc899c9b27dfd004e75ee73ef9071ad6835f9ff97f156f58c
default-4qgrufar
default-x8de1kjq
2022-09-08T11:44:42 info Executing pipeline RunConfig in CreateProcessor.
2022-09-08T11:44:42 info Executing pipeline MountRootfs in CreateProcessor.
which: no docker in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin)
INFO [2022-09-08 11:44:48] >> check root,port,cri success
Created symlink from /etc/systemd/system/multi-user.target.wants/containerd.service to /etc/systemd/system/containerd.service.
INFO [2022-09-08 11:44:50] >> Health check containerd!
INFO [2022-09-08 11:44:50] >> containerd is running
INFO [2022-09-08 11:44:50] >> init containerd success
Created symlink from /etc/systemd/system/multi-user.target.wants/image-cri-shim.service to /etc/systemd/system/image-cri-shim.service.
INFO [2022-09-08 11:44:50] >> Health check image-cri-shim!
INFO [2022-09-08 11:44:50] >> image-cri-shim is running
INFO [2022-09-08 11:44:50] >> init shim success
* Applying /usr/lib/sysctl.d/00-system.conf ...
net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
* Applying /usr/lib/sysctl.d/10-default-yama-scope.conf ...
* Applying /usr/lib/sysctl.d/50-default.conf ...
kernel.sysrq = 16
kernel.core_uses_pid = 1
kernel.kptr_restrict = 1
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.all.accept_source_route = 0
net.ipv4.conf.default.promote_secondaries = 1
net.ipv4.conf.all.promote_secondaries = 1
fs.protected_hardlinks = 1
fs.protected_symlinks = 1
* Applying /etc/sysctl.d/50-ecloud.conf ...
vm.swappiness = 0
net.ipv4.neigh.default.gc_stale_time = 120
net.ipv4.tcp_max_tw_buckets = 5000
net.ipv4.tcp_syncookies = 1
net.ipv4.tcp_fin_timeout = 30
net.ipv4.tcp_max_syn_backlog = 8192
net.ipv4.tcp_synack_retries = 2
net.netfilter.nf_conntrack_max = 655350
net.netfilter.nf_conntrack_tcp_timeout_established = 1200
kernel.sysrq = 1
kernel.hung_task_timeout_secs = 240
kernel.panic_on_oops = 1
kernel.hardlockup_panic = 1
* Applying /etc/sysctl.d/99-sysctl.conf ...
net.ipv4.conf.all.accept_redirects = 0
* Applying /etc/sysctl.d/k8s.conf ...
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.conf.all.rp_filter = 0
* Applying /etc/sysctl.conf ...
net.ipv4.conf.all.accept_redirects = 0
net.ipv4.ip_forward = 1
INFO [2022-09-08 11:44:50] >> init kube success
INFO [2022-09-08 11:44:50] >> init containerd rootfs success
2022-09-08T11:44:53 info Executing pipeline Init in CreateProcessor.
2022-09-08T11:44:53 info start to copy kubeadm config to master0
2022-09-08T11:44:53 info start to generate cert and kubeConfig...
2022-09-08T11:44:53 info start to generator cert and copy to masters...
2022-09-08T11:44:54 info apiserver altNames : {map[apiserver.cluster.local:apiserver.cluster.local apps-master1:apps-master1 kubernetes:kubernetes kubernetes.default:kubernetes.default kubernetes.default.svc:kubernetes.default.svc kubernetes.default.svc.cluster.local:kubernetes.default.svc.cluster.local localhost:localhost] map[10.103.97.2:10.103.97.2 10.96.0.1:10.96.0.1 127.0.0.1:127.0.0.1 192.168.0.10:192.168.0.10]}
2022-09-08T11:44:54 info Etcd altnames : {map[apps-master1:apps-master1 localhost:localhost] map[127.0.0.1:127.0.0.1 192.168.0.10:192.168.0.10 ::1:::1]}, commonName : apps-master1
2022-09-08T11:44:55 info start to copy etc pki files to masters
2022-09-08T11:44:55 info start to create kubeconfig...
2022-09-08T11:44:56 info start to copy kubeconfig files to masters
2022-09-08T11:44:56 info start to copy static files to masters
2022-09-08T11:44:56 info start to apply registry
unpacking docker.io/library/registry:2.7.1 (sha256:49bd6b1420deba16b51bd073977ea6ae4000b816a356b12e805a699c4e5d3dba)...done
25a239d4222d8b80780e8961c2c1babfed4b082254b6522c7b9b4859f22f3c37
INFO [2022-09-08 11:44:57] >> init registry success
2022-09-08T11:44:57 info start to init master0...
2022-09-08T11:44:57 info registry auth in node 192.168.0.10:22
2022-09-08T11:44:57 info domain sealos.hub delete success
2022-09-08T11:44:57 info domain sealos.hub:192.168.0.10 append success
2022-09-08T11:44:57 info domain apiserver.cluster.local delete success
2022-09-08T11:44:57 info domain apiserver.cluster.local:192.168.0.10 append success
W0908 11:44:57.884659 7310 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
[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'
已解决,不能指定:--env registryData=/data/cri/lib/registry
已解决,不能指定:--env registryData=/data/cri/lib/registry
其实指定registryData意义不是很大,这只是一个软链接,数据还是在sealos目录
--env registryData=/data/cri/lib/registry 不管用
https://github.com/labring-actions/bug-verify/actions/runs/4211974573/jobs/7310676596 测试通过 4.1.5-rc1
docker的参数是 --env data-root=/data/ 对么