单机部署sealos失败，请路过的大佬们看看是什么情况 #4941

alexcdever · 2024-08-01T14:29:08Z

alexcdever
Aug 1, 2024

我的部署环境是hyper-v中的Ubuntu 24.04 LTS，虚拟机硬件配置如下：

 neofetch
            .-/+oossssoo+/-.               root@sealos
        `:+ssssssssssssssssss+:`           -----------
      -+ssssssssssssssssssyyssss+-         OS: Ubuntu 24.04 LTS x86_64
    .ossssssssssssssssssdMMMNysssso.       Host: Virtual Machine Hyper-V UEFI Release v4.1
   /ssssssssssshdmmNNmmyNMMMMhssssss/      Kernel: 6.8.0-38-generic
  +ssssssssshmydMMMMMMMNddddyssssssss+     Uptime: 12 days, 10 hours, 58 mins
 /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/    Packages: 809 (dpkg)
.ssssssssdMMMNhsssssssssshNMMMdssssssss.   Shell: zsh 5.9
+sssshhhyNMMNyssssssssssssyNMMMysssssss+   Terminal: /dev/pts/0
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   CPU: 13th Gen Intel i7-13700K (12) @ 5.317GHz
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   Memory: 1340MiB / 16408MiB
+sssshhhyNMMNyssssssssssssyNMMMysssssss+
.ssssssssdMMMNhsssssssssshNMMMdssssssss.
 /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/
  +sssssssssdmydMMMMMMMMddddyssssssss+
   /ssssssssssshdmNNNNmyNMMMMhssssss/
    .ossssssssssssssssssdMMMNysssso.
      -+sssssssssssssssssyyyssss+-
        `:+ssssssssssssssssss+:`
            .-/+oossssoo+/-.

我使用的是license.sealos.io里在线安装提供的命令：

curl -sfL https://raw.githubusercontent.com/labring/sealos/v5.0.0/scripts/cloud/install.sh -o /tmp/install.sh && bash /tmp/install.sh --zh  \
 --cloud-version=v5.0.0 \
 --pod-cidr=100.64.0.0/10 \
 --service-cidr=10.96.0.0/22 \
 --cloud-domain=sealos.lan \
 --cloud-port=443 \
 --ssh-private-key=/root/.ssh/id_rsa \
 --kubernetes-version=1.27.11

执行后完整的输出信息如下：

 ~ curl -sfL https://raw.githubusercontent.com/labring/sealos/v5.0.0/scripts/cloud/install.sh -o /tmp/install.sh && bash /tmp/install.sh --zh  \
 --cloud-version=v5.0.0 \
 --pod-cidr=100.64.0.0/10 \
 --service-cidr=10.96.0.0/22 \
 --cloud-domain=sealos.lan \
 --cloud-port=443 \
 --ssh-private-key=/root/.ssh/id_rsa \
 --kubernetes-version=1.27.11
Sealos CLI is already installed.
依赖 iptables, 请确保 iptables 已经安装, 多节点需要配置 ssh 免密登录或密码一致, 使用 Sealos 提供的自签证书安装 完成后需要自信任证书
正在拉取镜像: sealos-cloud:v5.0.0
请输入 Master IP (单节点安装可输入回车跳过该步骤; 多个 Master 节点使用逗号分隔, 例: 192.168.0.1,192.168.0.2,192.168.0.3):
请输入 ssh 私钥路径 (回车使用默认值: '/root/.ssh/id_rsa'):
请输入 ssh 密码 (回车使用免密登录):
请输入证书路径 (回车使用 Sealos 提供的自签证书):
正在安装 Kubernetes 集群.
2024-08-01T10:35:15 info Start to create a new cluster: master [192.168.31.105], worker [], registry 192.168.31.105
2024-08-01T10:35:15 info Executing pipeline Check in CreateProcessor.
2024-08-01T10:35:15 info checker:hostname [192.168.31.105:22]
2024-08-01T10:35:15 info checker:timeSync [192.168.31.105:22]
2024-08-01T10:35:15 info Executing pipeline PreProcess in CreateProcessor.
2024-08-01T10:35:15 info Executing pipeline RunConfig in CreateProcessor.
2024-08-01T10:35:15 info Executing pipeline MountRootfs in CreateProcessor.
2024-08-01T10:35:16 info Executing pipeline MirrorRegistry in CreateProcessor.
2024-08-01T10:35:16 info trying default http mode to sync images to hosts [192.168.31.105:22]
2024-08-01T10:35:17 info Executing pipeline Bootstrap in CreateProcessor
 INFO [2024-08-01 10:35:17] >> Check port kubelet port 10249..10259, reserved port 5050..5054 inuse. Please wait...
 INFO [2024-08-01 10:35:17] >> check root,port,cri success
2024-08-01T10:35:17 info domain sealos.hub:192.168.31.105 append success
Created symlink /etc/systemd/system/multi-user.target.wants/registry.service → /etc/systemd/system/registry.service.
 INFO [2024-08-01 10:35:17] >> Health check registry!
 INFO [2024-08-01 10:35:17] >> registry is running
 INFO [2024-08-01 10:35:17] >> init registry success
2024-08-01T10:35:17 info domain apiserver.cluster.local:192.168.31.105 append success
Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /etc/systemd/system/containerd.service.
 INFO [2024-08-01 10:35:19] >> Health check containerd!
 INFO [2024-08-01 10:35:19] >> containerd is running
 INFO [2024-08-01 10:35:19] >> init containerd success
Created symlink /etc/systemd/system/multi-user.target.wants/image-cri-shim.service → /etc/systemd/system/image-cri-shim.service.
 INFO [2024-08-01 10:35:19] >> Health check image-cri-shim!
 INFO [2024-08-01 10:35:19] >> image-cri-shim is running
 INFO [2024-08-01 10:35:19] >> init shim success
127.0.0.1 localhost
::1 ip6-localhost ip6-loopback
Firewall stopped and disabled on system startup
* Applying /usr/lib/sysctl.d/10-apparmor.conf ...
* Applying /etc/sysctl.d/10-console-messages.conf ...
* Applying /etc/sysctl.d/10-ipv6-privacy.conf ...
* Applying /etc/sysctl.d/10-kernel-hardening.conf ...
* Applying /etc/sysctl.d/10-magic-sysrq.conf ...
* Applying /etc/sysctl.d/10-map-count.conf ...
* Applying /etc/sysctl.d/10-network-security.conf ...
* Applying /etc/sysctl.d/10-ptrace.conf ...
* Applying /etc/sysctl.d/10-zeropage.conf ...
* Applying /usr/lib/sysctl.d/50-pid-max.conf ...
* Applying /usr/lib/sysctl.d/99-protect-links.conf ...
* Applying /etc/sysctl.d/99-sysctl.conf ...
* Applying /etc/sysctl.d/99-zzz-override_cilium.conf ...
* Applying /etc/sysctl.conf ...
kernel.apparmor_restrict_unprivileged_userns = 1
kernel.printk = 4 4 1 7
net.ipv6.conf.all.use_tempaddr = 2
net.ipv6.conf.default.use_tempaddr = 2
kernel.kptr_restrict = 1
kernel.sysrq = 176
vm.max_map_count = 1048576
net.ipv4.conf.default.rp_filter = 2
net.ipv4.conf.all.rp_filter = 2
kernel.yama.ptrace_scope = 1
vm.mmap_min_addr = 65536
kernel.pid_max = 4194304
fs.protected_fifos = 1
fs.protected_hardlinks = 1
fs.protected_regular = 2
fs.protected_symlinks = 1
fs.file-max = 1048576 # sealos
net.bridge.bridge-nf-call-ip6tables = 1 # sealos
net.bridge.bridge-nf-call-iptables = 1 # sealos
net.core.somaxconn = 65535 # sealos
net.ipv4.conf.all.rp_filter = 0 # sealos
net.ipv4.ip_forward = 1 # sealos
net.ipv4.ip_local_port_range = 1024 65535 # sealos
net.ipv4.tcp_keepalive_intvl = 30 # sealos
net.ipv4.tcp_keepalive_time = 600 # sealos
net.ipv4.vs.conn_reuse_mode = 0 # sealos
net.ipv4.vs.conntrack = 1 # sealos
net.ipv6.conf.all.forwarding = 1 # sealos
net.ipv4.conf.cilium_host.rp_filter = 0
net.ipv4.conf.cilium_net.rp_filter = 0
net.ipv4.conf.cilium_vxlan.rp_filter = 0
net.ipv4.conf.all.rp_filter = 0
fs.file-max = 1048576 # sealos
net.bridge.bridge-nf-call-ip6tables = 1 # sealos
net.bridge.bridge-nf-call-iptables = 1 # sealos
net.core.somaxconn = 65535 # sealos
net.ipv4.conf.all.rp_filter = 0 # sealos
net.ipv4.ip_forward = 1 # sealos
net.ipv4.ip_local_port_range = 1024 65535 # sealos
net.ipv4.tcp_keepalive_intvl = 30 # sealos
net.ipv4.tcp_keepalive_time = 600 # sealos
net.ipv4.vs.conn_reuse_mode = 0 # sealos
net.ipv4.vs.conntrack = 1 # sealos
net.ipv6.conf.all.forwarding = 1 # sealos
 INFO [2024-08-01 10:35:19] >> pull pause image sealos.hub:5000/pause:3.9
Image is up to date for sha256:e6f1816883972d4be47bd48879a08919b96afcd344132622e4d444987919323c
Created symlink /etc/systemd/system/multi-user.target.wants/kubelet.service → /etc/systemd/system/kubelet.service.
 INFO [2024-08-01 10:35:20] >> init kubelet success
 INFO [2024-08-01 10:35:20] >> init rootfs success
2024-08-01T10:35:20 info Executing pipeline Init in CreateProcessor.
2024-08-01T10:35:20 info Copying kubeadm config to master0
2024-08-01T10:35:20 info start to generate cert and kubeConfig...
2024-08-01T10:35:20 info start to generate and copy certs to masters...
2024-08-01T10:35:20 info apiserver altNames : {map[apiserver.cluster.local:apiserver.cluster.local kubernetes:kubernetes kubernetes.default:kubernetes.default kubernetes.default.svc:kubernetes.default.svc kubernetes.default.svc.cluster.local:kubernetes.default.svc.cluster.local localhost:localhost sealos:sealos] 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.31.105:192.168.31.105]}
2024-08-01T10:35:20 info Etcd altnames : {map[localhost:localhost sealos:sealos] map[127.0.0.1:127.0.0.1 192.168.31.105:192.168.31.105 ::1:::1]}, commonName : sealos
2024-08-01T10:35:21 info start to copy etc pki files to masters
2024-08-01T10:35:21 info start to create kubeconfig...
2024-08-01T10:35:21 info start to copy kubeconfig files to masters
2024-08-01T10:35:21 info start to copy static files to masters
2024-08-01T10:35:21 info start to init master0...
[config/images] Pulled registry.k8s.io/kube-apiserver:v1.27.11
[config/images] Pulled registry.k8s.io/kube-controller-manager:v1.27.11
[config/images] Pulled registry.k8s.io/kube-scheduler:v1.27.11
[config/images] Pulled registry.k8s.io/kube-proxy:v1.27.11
[config/images] Pulled registry.k8s.io/pause:3.9
[config/images] Pulled registry.k8s.io/etcd:3.5.10-0
[config/images] Pulled registry.k8s.io/coredns/coredns:v1.10.1
W0801 10:35:26.444943 1244609 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: 127.0.0.1; the provided value is: 0.0.0.0
[init] Using Kubernetes version: v1.27.11
[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'
W0801 10:35:26.515046 1244609 checks.go:835] detected that the sandbox image "sealos.hub:5000/pause:3.9" of the container runtime is inconsistent with that used by kubeadm. It is recommended that using "registry.k8s.io/pause:3.9" as the CRI sandbox image.
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[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] Using existing etcd/ca certificate authority
[certs] Using existing etcd/server certificate and key on disk
[certs] Using existing etcd/peer certificate and key on disk
[certs] Using existing etcd/healthcheck-client certificate and key on disk
[certs] Using existing apiserver-etcd-client certificate and key on disk
[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"
W0801 10:35:26.744008 1244609 kubeconfig.go:264] a kubeconfig file "/etc/kubernetes/controller-manager.conf" exists already but has an unexpected API Server URL: expected: https://192.168.31.105:6443, got: https://apiserver.cluster.local:6443
[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/controller-manager.conf"
W0801 10:35:26.781829 1244609 kubeconfig.go:264] a kubeconfig file "/etc/kubernetes/scheduler.conf" exists already but has an unexpected API Server URL: expected: https://192.168.31.105:6443, got: https://apiserver.cluster.local:6443
[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/scheduler.conf"
[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] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[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 4m0s
[apiclient] All control plane components are healthy after 3.503001 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config" in namespace kube-system with the configuration for the kubelets in the cluster
[upload-certs] Skipping phase. Please see --upload-certs
[mark-control-plane] Marking the node sealos as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes
[bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
[kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key
[addons] Applied essential addon: CoreDNS

Your Kubernetes control-plane has initialized successfully!

To start using your cluster, you need to run the following as a regular user:

  mkdir -p $HOME/.kube
  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  sudo chown $(id -u):$(id -g) $HOME/.kube/config

Alternatively, if you are the root user, you can run:

  export KUBECONFIG=/etc/kubernetes/admin.conf

You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
  https://kubernetes.io/docs/concepts/cluster-administration/addons/

You can now join any number of control-plane nodes by copying certificate authorities
and service account keys on each node and then running the following as root:

  kubeadm join apiserver.cluster.local:6443 --token <value withheld> \
        --discovery-token-ca-cert-hash sha256:a80eb81690a38d80e84910a30ee01d0b9a1236717aa08c06bc1f203cc1b72009 \
        --control-plane --certificate-key <value withheld>

Then you can join any number of worker nodes by running the following on each as root:

kubeadm join apiserver.cluster.local:6443 --token <value withheld> \
        --discovery-token-ca-cert-hash sha256:a80eb81690a38d80e84910a30ee01d0b9a1236717aa08c06bc1f203cc1b72009
2024-08-01T10:35:31 info Executing pipeline Join in CreateProcessor.
2024-08-01T10:35:31 info Executing pipeline RunGuest in CreateProcessor.
2024-08-01T10:35:31 info succeeded in creating a new cluster, enjoy it!
2024-08-01T10:35:31 info
      ___           ___           ___           ___       ___           ___
     /\  \         /\  \         /\  \         /\__\     /\  \         /\  \
    /::\  \       /::\  \       /::\  \       /:/  /    /::\  \       /::\  \
   /:/\ \  \     /:/\:\  \     /:/\:\  \     /:/  /    /:/\:\  \     /:/\ \  \
  _\:\~\ \  \   /::\~\:\  \   /::\~\:\  \   /:/  /    /:/  \:\  \   _\:\~\ \  \
 /\ \:\ \ \__\ /:/\:\ \:\__\ /:/\:\ \:\__\ /:/__/    /:/__/ \:\__\ /\ \:\ \ \__\
 \:\ \:\ \/__/ \:\~\:\ \/__/ \/__\:\/:/  / \:\  \    \:\  \ /:/  / \:\ \:\ \/__/
  \:\ \:\__\    \:\ \:\__\        \::/  /   \:\  \    \:\  /:/  /   \:\ \:\__\
   \:\/:/  /     \:\ \/__/        /:/  /     \:\  \    \:\/:/  /     \:\/:/  /
    \::/  /       \:\__\         /:/  /       \:\__\    \::/  /       \::/  /
     \/__/         \/__/         \/__/         \/__/     \/__/         \/__/

                  Website: https://www.sealos.io/
                  Address: github.com/labring/sealos
                  Version: 5.0.0-beta5-a0b3363d9

正在使用 Cilium 作为网络插件, 主机系统必须满足以下要求:
1.具有AMD64或AArch64架构的主机;
2.Linux内核> = 4.19.57或等效版本 (例如, 在RHEL8上为4.18).
2024-08-01T10:35:31 info start to install app in this cluster
2024-08-01T10:35:31 info Executing SyncStatusAndCheck Pipeline in InstallProcessor
2024-08-01T10:35:31 info Executing ConfirmOverrideApps Pipeline in InstallProcessor
2024-08-01T10:35:31 info Executing PreProcess Pipeline in InstallProcessor
2024-08-01T10:35:31 info Executing pipeline MountRootfs in InstallProcessor.
2024-08-01T10:35:32 info Executing pipeline MirrorRegistry in InstallProcessor.
2024-08-01T10:35:32 info trying default http mode to sync images to hosts [192.168.31.105:22]
2024-08-01T10:35:33 info Executing UpgradeIfNeed Pipeline in InstallProcessor
ℹ️  Using Cilium version 1.14.8
🔮 Auto-detected cluster name: kubernetes
🔮 Auto-detected kube-proxy has not been installed
ℹ️  Cilium will fully replace all functionalities of kube-proxy
2024-08-01T10:35:34 info succeeded install app in this cluster
2024-08-01T10:35:34 info no nodes that need to be scaled
2024-08-01T10:35:34 info
      ___           ___           ___           ___       ___           ___
     /\  \         /\  \         /\  \         /\__\     /\  \         /\  \
    /::\  \       /::\  \       /::\  \       /:/  /    /::\  \       /::\  \
   /:/\ \  \     /:/\:\  \     /:/\:\  \     /:/  /    /:/\:\  \     /:/\ \  \
  _\:\~\ \  \   /::\~\:\  \   /::\~\:\  \   /:/  /    /:/  \:\  \   _\:\~\ \  \
 /\ \:\ \ \__\ /:/\:\ \:\__\ /:/\:\ \:\__\ /:/__/    /:/__/ \:\__\ /\ \:\ \ \__\
 \:\ \:\ \/__/ \:\~\:\ \/__/ \/__\:\/:/  / \:\  \    \:\  \ /:/  / \:\ \:\ \/__/
  \:\ \:\__\    \:\ \:\__\        \::/  /   \:\  \    \:\  /:/  /   \:\ \:\__\
   \:\/:/  /     \:\ \/__/        /:/  /     \:\  \    \:\/:/  /     \:\/:/  /
    \::/  /       \:\__\         /:/  /       \:\__\    \::/  /       \::/  /
     \/__/         \/__/         \/__/         \/__/     \/__/         \/__/

                  Website: https://www.sealos.io/
                  Address: github.com/labring/sealos
                  Version: 5.0.0-beta5-a0b3363d9

正在等待集群就绪, 如果您想跳过此步骤, 请输入'y':  ...y
2024-08-01T10:35:39 info start to install app in this cluster
2024-08-01T10:35:39 info Executing SyncStatusAndCheck Pipeline in InstallProcessor
2024-08-01T10:35:39 info Executing ConfirmOverrideApps Pipeline in InstallProcessor
2024-08-01T10:35:39 info Executing PreProcess Pipeline in InstallProcessor
2024-08-01T10:35:39 info Executing pipeline MountRootfs in InstallProcessor.
2024-08-01T10:35:39 info Executing pipeline MirrorRegistry in InstallProcessor.
2024-08-01T10:35:39 info trying default http mode to sync images to hosts [192.168.31.105:22]
2024-08-01T10:35:40 info Executing UpgradeIfNeed Pipeline in InstallProcessor
Release "cert-manager" does not exist. Installing it now.
Error: signal: killed
➜  ~ Error: client rate limiter Wait returned an error: context deadline exceeded

我试过了使用sealos reset --force重置，再执行部署命令，还是一样的结果，已经重复几次都是这样了，路过的大佬们如果知道这是什么原因，该怎么解决的话，烦请告知，谢谢~

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

单机部署sealos失败，请路过的大佬们看看是什么情况 #4941

{{title}}

Replies: 0 comments

Select a reply

单机部署sealos失败，请路过的大佬们看看是什么情况 #4941

alexcdever Aug 1, 2024

Replies: 0 comments

alexcdever
Aug 1, 2024