k8s新增节点组件未启动问题记录

发布时间:2023年12月18日

?背景:

新加的k8s节点内网主机,本地镜像已经存在,kube-proxy/caclico服务启动失败,查看pod日志报错如下

Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create containerd task: failed to create shim task: OCI runtime create failed: unable to retrieve OCI runtime error (open /run/containerd/io.containerd.runtime.v2.task/k8s.io/7ca04c9265248abe9341a0668f52ebfb62e08ee88f5753714e5edec35015c49c/log.json: no such file or directory): runc did not terminate successfully: exit status 127: unknown

通过journalctl -xefu containerd查看日志获取到如下信息

Sep 08 10:17:29 k8s-node containerd[27896]: time="2023-09-08T10:17:29.088325139+08:00" level=error msg="RunPodSandbox for &PodSandboxMetadata{Name:kube-proxy-dtggn,Uid:420081bc-91ea-42da-8791-1cfb3052fe39,Namespace:kube-system,Attempt:0,} failed, error" error="failed to create containerd task: failed to create shim task: OCI runtime create failed: unable to retrieve OCI runtime error (open /run/containerd/io.containerd.runtime.v2.task/k8s.io/df229da174a0ed25a0ad6bfa4fb6cec01d300047fbd4a13e1b4d2a39a0809038/log.json: no such file or directory): runc did not terminate successfully: exit status 127: unknown"

在主机使用runc命令发现报错

[root@k8s-node ~]# runc
runc: symbol lookup error: runc: undefined symbol: seccomp_notify_respond

【报错原因】?缺少依赖包libseccomp(需安装2.4以上版本)

【解决办法】 安装libseccomp 2.5.1

[root@k8s-node ~]# wget http://rpmfind.net/linux/centos/8-stream/BaseOS/x86_64/os/Packages/libseccomp-2.5.1-1.el8.x86_64.rpm
[root@k8s-node ~]# rpm -ivh libseccomp-2.5.1-1.el8.x86_64.rpm
[root@k8s-node ~]# rpm -qa |  grep libseccomp
libseccomp-2.5.1-1.el8.x86_64

?再次查看服务已正常启动

文章来源:https://blog.csdn.net/weixin_46775222/article/details/132755756
本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。