安装1.7.2 失败，"Failed to new image service" err="unable to determine image API version: rpc error: code = Unimplemented desc = unknown service runtime.v1.ImageService" runtimeType="containerd" runtimeURI="" runtimeRemoteURI="unix:///hostvarrun/containerd/containerd.sock"

openkruise / kruise

Automated management of large-scale applications on Kubernetes (incubating project under CNCF)

https://openkruise.io

Other

4.68k stars 768 forks source link

安装1.7.2 失败，"Failed to new image service" err="unable to determine image API version: rpc error: code = Unimplemented desc = unknown service runtime.v1.ImageService" runtimeType="containerd" runtimeURI="" runtimeRemoteURI="unix:///hostvarrun/containerd/containerd.sock" #1817

Open 1182986209 opened 2 weeks ago

1182986209 commented 2 weeks ago

What happened:

"Failed to new image service" err="unable to determine image API version: rpc error: code = Unimplemented desc = unknown service runtime.v1.ImageService" runtimeType="containerd" runtimeURI="" runtimeRemoteURI="unix:///hostvarrun/containerd/containerd.sock" What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

Kruise version: v1.7.2
Kubernetes version (use kubectl version): 1.23.10
Install details (e.g. helm install args):
Others:

1182986209 commented 2 weeks ago

cri： containerd

ABNER-1 commented 2 weeks ago

Since v1.6.0 (alpha/beta), KruiseDaemon will no longer support v1alpha2 CRI runtimes. However, it is still possible to use OpenKruise on Kubernetes clusters with nodes that only support v1alpha2 CRI, as long as KruiseDaemon is not enabled (install/upgrade Kruise charts with featureGates="KruiseDaemon=false").

Hello @1182986209 . Regarding the issue you mentioned, it's likely due to an outdated containerd version that doesn't support CRI v1.