kubernetes错误:跳过pod同步 [英] kubernetes error : skipping pod synchronization

查看:430
本文介绍了kubernetes错误:跳过pod同步的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经在centos 7上配置了kubernetes master,在另一个节点centos 7上配置了kubernetes节点

i have configured kubernetes master on centos 7 and kubernetes node on another node centos 7

在kube master上运行的服务:

  • kube-controller-manager
  • kube-apiserver
  • kube-scheduler
  • etcd
  • 绒布

在kube节点上运行的服务:

  • 绒布
  • docker
  • kube-proxy
  • 小玩意

所有服务都已启动并正在运行,我可以看到api url成功获取了所有端点. http://kube-master:8080 但是,当我运行命令kube get nodes时,出现以下错误:

all services are up and running and i could see the api url successfully getting all endpoints. http://kube-master:8080 however, when i am running command kube get nodes , getting following error :

skipping pod synchronization. container runtime is down

我没有得到此错误的含义以及如何解决此问题.请提出建议.

I am not getting what this error means and how to resolve this. Please suggest.

推荐答案

kubelet是唯一依赖于容器运行时的组件(在您的情况下为Docker).如果您是我,那么我将开始研究kubelet日志并搜索对Docker的引用.也许配置为运行kubelet的用户没有必要的权限才能与/var/run/docker.sock上的Docker套接字进行交互.

kubelet is the only component with a dependency on the container runtime (Docker in your case). If I were you I'd start investigating the kubelet logs and search for references to Docker. Maybe the user configured to run kubelet doesn't have the necessary permissions to interact with the Docker socket at /var/run/docker.sock.

如果您需要进一步的帮助,日志的内容可能会有所帮助.

The content of your logs may help if you need further help.

这篇关于kubernetes错误:跳过pod同步的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆