labring
sealos部署k8s v1.32.5集群错误
Sealos Version
v5.0.1
How to reproduce the bug?
拉取的版本是：docker pull labring/kubernetes:v1.33.1-5.0.1 到自己的harbar仓库中
执行
sealos gen harbor.paas.nl:10081/paas_public/kube-system/kubernetes-sealos:v1.33.1-5.0.1 \ harbor.paas.nl:10081/paas_public/kube-system/helm:v3.10.3 \ harbor.paas.nl:10081/paas_public/kube-system/calico:v3.25.0 \ --masters 10.1.21.175 --nodes 10.1.21.176 \ --env criData=/paas/containerd,registryDomain=harbor.paas.nl,registryUsername=admin,registryPassword=Nlpaas123,registryPort1:80,registryPort1:10081 \ --pk /root/.ssh/id_rsa --user=root --cluster test131 > /root/cluster-file/test131/Clusterfile
然后执行： sealos apply -f Clusterfile --debug
最后报错：
Error: failed to init masters: master pull image failed, error: run command kubeadm config images pull --cri-socket unix:///var/run/image-cri-shim.sock --kubernetes-version v1.32.5 -v 6on 10.1.21.175:22, output: I0610 18:39:09.550114 588091 interface.go:432] Looking for default routes with IPv4 addresses I0610 18:39:09.550175 588091 interface.go:437] Default route transits interface "ens192" I0610 18:39:09.550494 588091 interface.go:209] Interface ens192 is up I0610 18:39:09.550554 588091 interface.go:257] Interface "ens192" has 3 addresses :[10.1.21.175/24 10:1:21::175/64 fe80::250:56ff:fe9f:2775/64]. I0610 18:39:09.550570 588091 interface.go:224] Checking addr 10.1.21.175/24. I0610 18:39:09.550579 588091 interface.go:231] IP found 10.1.21.175 I0610 18:39:09.550602 588091 interface.go:263] Found valid IPv4 address 10.1.21.175 for interface "ens192". I0610 18:39:09.550611 588091 interface.go:443] Found active IP 10.1.21.175 I0610 18:39:09.550630 588091 kubelet.go:196] the value of KubeletConfiguration.cgroupDriver is empty; setting it to "systemd" validate service connection: validate CRI v1 runtime API for endpoint "unix:///var/run/image-cri-shim.sock": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService failed to create new CRI runtime service k8s.io/kubernetes/cmd/kubeadm/app/util/runtime.(*CRIRuntime).Connect k8s.io/kubernetes/cmd/kubeadm/app/util/runtime/runtime.go:83 k8s.io/kubernetes/cmd/kubeadm/app/cmd.newCmdConfigImagesPull.func1 k8s.io/kubernetes/cmd/kubeadm/app/cmd/config.go:387 github.com/spf13/cobra.(*Command).execute github.com/spf13/[email protected]/command.go:985 github.com/spf13/cobra.(*Command).ExecuteC github.com/spf13/[email protected]/command.go:1117 github.com/spf13/cobra.(*Command).Execute github.com/spf13/[email protected]/command.go:1041 k8s.io/kubernetes/cmd/kubeadm/app.Run k8s.io/kubernetes/cmd/kubeadm/app/kubeadm.go:47 main.main k8s.io/kubernetes/cmd/kubeadm/kubeadm.go:25 runtime.main runtime/proc.go:272 runtime.goexit runtime/asm_amd64.s:1700 , error: Process exited with status 1,
我用1.29.9不会报错，1.32.5和1.33.1都会报同样的错误 containerd版本是：v1.6.15
错误如何解决呢
What is the expected behavior?
No response
What do you see instead?
No response
Operating environment
- Sealos version:
- Docker version:
- Kubernetes version:
- Operating system:
- Runtime environment:
- Cluster size:
- Additional information:
Additional information
No response
I also encountered the same problem. Enabling the debug log can view detailed information.
The problem comes from the image-cri-shim. It does not implement the RuntimeService. But the newer version of kubeadm will also access RuntimeService even when pulling images.
I think this can only be solved by changing the code of sealos or image-cri-shim. Maintainers please take a look at this issue. @bxy4543 @zzjin
