Kubernetes 失败的CreatePodSandbox&;kubelet,$(奴隶名称)吊舱沙箱已更改,它将被杀死并重新创建

Kubernetes 失败的CreatePodSandbox&;kubelet,$(奴隶名称)吊舱沙箱已更改,它将被杀死并重新创建,kubernetes,Kubernetes,我在“仿生海狸”ubuntu上运行一个有6个节点的kubernetes cluter(cluser master和kubernetes slave0-4),我使用的是Weave 为了安装kubernetes,我遵循并安装了weave,安装了这里推荐的任何东西,然后将其清除(它不再显示在我的播客中) kubectl get pods--所有名称空间返回: NAMESPACE NAME READY STATUS

我在“仿生海狸”ubuntu上运行一个有6个节点的kubernetes cluter(cluser master和kubernetes slave0-4),我使用的是Weave 为了安装kubernetes,我遵循并安装了weave,安装了这里推荐的任何东西,然后将其清除(它不再显示在我的播客中)

kubectl get pods--所有名称空间
返回:

NAMESPACE     NAME                                     READY   STATUS              RESTARTS   AGE
kube-system   coredns-fb8b8dccf-g8psp                  0/1     ContainerCreating   0          77m
kube-system   coredns-fb8b8dccf-pbfr7                  0/1     ContainerCreating   0          77m
kube-system   etcd-cluster-master                      1/1     Running             5          77m
kube-system   kube-apiserver-cluster-master            1/1     Running             5          77m
kube-system   kube-controller-manager-cluster-master   1/1     Running             5          77m
kube-system   kube-proxy-72s98                         1/1     Running             5          73m
kube-system   kube-proxy-cqmdm                         1/1     Running             3          63m
kube-system   kube-proxy-hgnpj                         1/1     Running             0          69m
kube-system   kube-proxy-nhjdc                         1/1     Running             5          72m
kube-system   kube-proxy-sqvdd                         1/1     Running             5          77m
kube-system   kube-proxy-vmg9k                         1/1     Running             0          70m
kube-system   kube-scheduler-cluster-master            1/1     Running             5          76m
kube-system   kubernetes-dashboard-5f7b999d65-p7clv    0/1     ContainerCreating   0          61m
kube-system   weave-net-2brvt                          2/2     Running             0          69m
kube-system   weave-net-5wlks                          2/2     Running             16         72m
kube-system   weave-net-65qmd                          2/2     Running             16         73m
kube-system   weave-net-9x8cz                          2/2     Running             9          63m
kube-system   weave-net-r2nhz                          2/2     Running             15         75m
kube-system   weave-net-stq8x                          2/2     Running             0          70m
如果我使用
kubectl descripe$(kube dashboard pod name)--namespace=kube system
它返回:

NAME                                    READY   STATUS              RESTARTS   AGE
kubernetes-dashboard-5f7b999d65-p7clv   0/1     ContainerCreating   0          64m
rock64@cluster-master:~$
rock64@cluster-master:~$ kubectl describe pods kubernetes-dashboard-5f7b999d65-p7clv --namespace=kube-system
Name:               kubernetes-dashboard-5f7b999d65-p7clv
Namespace:          kube-system
Priority:           0
PriorityClassName:  <none>
Node:               kubernetes-slave1/10.0.0.215
Start Time:         Sun, 14 Apr 2019 10:20:42 +0000
Labels:             k8s-app=kubernetes-dashboard
                    pod-template-hash=5f7b999d65
Annotations:        <none>
Status:             Pending
IP:
Controlled By:      ReplicaSet/kubernetes-dashboard-5f7b999d65
Containers:
  kubernetes-dashboard:
    Container ID:
    Image:         k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1
    Image ID:
    Port:          8443/TCP
    Host Port:     0/TCP
    Args:
      --auto-generate-certificates
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Liveness:       http-get https://:8443/ delay=30s timeout=30s period=10s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /certs from kubernetes-dashboard-certs (rw)
      /tmp from tmp-volume (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kubernetes-dashboard-token-znrkr (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  kubernetes-dashboard-certs:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  kubernetes-dashboard-certs
    Optional:    false
  tmp-volume:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  kubernetes-dashboard-token-znrkr:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  kubernetes-dashboard-token-znrkr
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node-role.kubernetes.io/master:NoSchedule
                 node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason                  Age                     From                        Message
  ----     ------                  ----                    ----                        -------
  Normal   Scheduled               64m                     default-scheduler           Successfully assigned kube-system/kubernetes-dashboard-5f7b999d65-p7clv to kubernetes-slave1
  Warning  FailedCreatePodSandBox  64m                     kubelet, kubernetes-slave1  Failed create pod sandbox: rpc error: code = Unknown desc = [failed to set up sandbox container "4e6d9873f49a02e86cef79e338ce97162291897b2aaad1ddb99c5e066ed42178" network for pod "kubernetes-dashboard-5f7b999d65-p7clv": NetworkPlugin cni failed to set up pod "kubernetes-dashboard-5f7b999d65-p7clv_kube-system" network: failed to find plugin "loopback" in path [/opt/cni/bin], failed to clean up sandbox container "4e6d9873f49a02e86cef79e338ce97162291897b2aaad1ddb99c5e066ed42178" network for pod "kubernetes-dashboard-5f7b999d65-p7clv": NetworkPlugin cni failed to teardown pod "kubernetes-dashboard-5f7b999d65-p7clv_kube-system" network: failed to find plugin "portmap" in path [/opt/cni/bin]]
  Normal   SandboxChanged          59m (x25 over 64m)      kubelet, kubernetes-slave1  Pod sandbox changed, it will be killed and re-created.
  Normal   SandboxChanged          49m (x18 over 53m)      kubelet, kubernetes-slave1  Pod sandbox changed, it will be killed and re-created.
  Normal   SandboxChanged          46m (x13 over 48m)      kubelet, kubernetes-slave1  Pod sandbox changed, it will be killed and re-created.
  Normal   SandboxChanged          24m (x94 over 44m)      kubelet, kubernetes-slave1  Pod sandbox changed, it will be killed and re-created.
  Normal   SandboxChanged          4m12s (x26 over 9m52s)  kubelet, kubernetes-slave1  Pod sandbox changed, it will be killed and re-created.```
名称就绪状态重新启动
kubernetes-dashboard-5f7b999d65-p7clv 0/1集装箱制造0 64m
rock64@cluster-大师:~$
rock64@cluster-master:~$kubectl描述pods kubernetes-dashboard-5f7b999d65-p7clv--namespace=kube系统
名称:kubernetes-dashboard-5f7b999d65-p7clv
名称空间:kube系统
优先级:0
PriorityClassName:
节点:kubernetes-slave1/10.0.0.215
开始时间:2019年4月14日星期日10:20:42+0000
标签:k8s app=kubernetes仪表板
pod模板哈希=5f7b999d65
注释:
状态:待定
知识产权:
控制人:ReplicaSet/kubernetes-dashboard-5F7B99D65
容器:
kubernetes仪表板:
容器ID:
图片:k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1
图像ID:
端口:8443/TCP
主机端口:0/TCP
Args:
--自动生成证书
国家:等待
原因:集装箱制造
就绪:错误
重新启动计数:0
活跃度:http get https://:8443/延迟=30s超时=30s周期=10s#成功=1#失败=3
环境:
挂载:
/来自kubernetes仪表板证书(rw)的证书
/来自tmp卷(rw)的tmp
/var/run/secrets/kubernetes.io/serviceaccount来自kubernetes仪表盘令牌znrkr(ro)
条件:
类型状态
初始化为True
准备错误
集装箱准备好了吗
播客预定为真
卷数:
kubernetes仪表板证书:
类型:Secret(由Secret填充的卷)
SecretName:kubernetes仪表板证书
可选:false
tmp卷:
类型:EmptyDir(共享pod生存期的临时目录)
中等:
SizeLimit:
kubernetes仪表盘标记znrkr:
类型:Secret(由Secret填充的卷)
SecretName:kubernetes仪表盘令牌znrkr
可选:false
QoS等级:最佳努力
节点选择器:
容差:节点角色.kubernetes.io/master:NoSchedule
node.kubernetes.io/not ready:NoExecute持续300秒
node.kubernetes.io/不可访问:不执行300秒
活动:
从消息中键入原因年龄
----     ------                  ----                    ----                        -------
正常计划的64m默认计划程序已成功将kube system/kubernetes-dashboard-5f7b999d65-p7clv分配给kubernetes-slave1
警告FailedCreatePodSandBox 64m kubelet,kubernetes-slave1未能创建pod sandbox:rpc错误:代码=未知描述=[未能设置沙盒容器“4E6D9873F49A02E86CEF7938CE97162291897B2AAD1DDB99C5E066ED42178”pod网络“kubernetes-dashboard-5f7b999d65-p7clv”:网络插件cni未能设置pod“kubernetes-dashboard-5f7b999d65-p7clv_kube-system”网络:未能在路径[/opt/cni/bin]中找到插件“环回”,未能清理沙箱容器“4E6D9873F49A02E86CEF7938CE97162291897B2AAD1DDB99C5E066ED42178”pod网络“kubernetes-dashboard-5F7B99D65-p7clv”:网络插件cni未能拆除pod”kubernetes-dashboard-5f7b999d65-p7clv_kube-system“网络:在路径[/opt/cni/bin]中找不到插件“端口图”
正常沙箱更改59m(x25/64m)kubelet,kubernetes-slave1吊舱沙箱更改,将杀死并重新创建。
正常沙箱更改49m(x18/53m)kubelet,kubernetes-slave1吊舱沙箱更改,它将被杀死并重新创建。
普通沙箱更改为46m(x13/48m)kubelet,kubernetes-slave1吊舱沙箱更改,它将被杀死并重新创建。
正常沙箱更改24m(x94超过44m)kubelet,kubernetes-slave1吊舱沙箱更改,它将被杀死并重新创建。
正常沙箱更改4m12s(x26超过9m52s)kubelet,kubernetes-slave1吊舱沙箱更改,将杀死并重新创建```
在路径[/opt/cni/bin]中找不到插件“环回”

正如帮助信息试图向您解释的那样,您的CNI安装似乎有问题。每当您看到
FailedCreatePodSandBox
SandboxChanged
,它总是(?)与CNI故障相关

很短的版本是抓取软件包,将其解包到
/opt/cni/bin
,确保它们是可执行的,然后重新启动…呃,可能是机器,但肯定是有问题的Pod,也可能是
kubelet

p、 你在这里会过得更愉快,因为这是一个非常常见的问题