containerd ps 失败_validate service connection: cri v1 runtime api is-CSDN博客

本文链接：https://blog.csdn.net/weixin_44552215/article/details/134436405

文章讲述了如何在Kubernetes中更新containerd的使用，从使用deprecated的defaultendpoints转向设置特定endpoint，以及在containerd运行后配置crictl和处理CRIv1runtimeAPI不实施的问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

containerd ps 失败

- runtime connect using default endpoints: [unix:///var/run/dockershim.sock unix:///run/containerd/containerd.sock unix:///run/crio/crio.sock unix:///var/run/cri-dockerd.sock]. As the default settings are now deprecated, you should set the endpoint instead.
- - FATA[0000] validate service connection: CRI v1 runtime API is not implemented for endpoint "unix:///var/run/containerd/containerd.sock": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService

containerd是轻量化的运行容器，类似于docker，目前是K8S推荐的首选运行容器

runtime connect using default endpoints: [unix:///var/run/dockershim.sock unix:///run/containerd/containerd.sock unix:///run/crio/crio.sock unix:///var/run/cri-dockerd.sock]. As the default settings are now deprecated, you should set the endpoint instead.

# 未运行前
crictl config runtime-endpoint unix:///var/run/cri-dockerd.sock
# containerd 以运行后 ()
crictl config runtime-endpoint unix:///var/run/containerd/containerd.sock
crictl ps -a

FATA[0000] validate service connection: CRI v1 runtime API is not implemented for endpoint “unix:///var/run/containerd/containerd.sock”: rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService

原帖地址：https://blog.csdn.net/weixin_52156647/article/details/129758753

vim /etc/containerd/config.toml

#如果看到了这行：
disabled_plugins : ["cri"]

#将这行用#注释或者将"cri"删除
#disabled_plugins : ["cri"]
 
disabled_plugins : []
#重启容器运行时
systemctl restart containerd