Docker 谷歌云上的Kubernetes 1.7:FailedSync错误同步pod,沙盒更改pod沙盒更改,它将被杀死并重新创建
我的Kubernetes吊舱和容器没有启动。他们被困在状态Docker 谷歌云上的Kubernetes 1.7:FailedSync错误同步pod,沙盒更改pod沙盒更改,它将被杀死并重新创建,docker,kubernetes,google-cloud-platform,google-kubernetes-engine,Docker,Kubernetes,Google Cloud Platform,Google Kubernetes Engine,我的Kubernetes吊舱和容器没有启动。他们被困在状态ContainerCreating中 我运行了命令kubectl descripe po pod name,该命令列出了事件,我看到了以下错误: Type Reason Message Warning FailedSync Error syncing pod Normal SandboxChanged Pod sandbox changed, it will be
ContainerCreating
中
我运行了命令kubectl descripe po pod name
,该命令列出了事件,我看到了以下错误:
Type Reason Message
Warning FailedSync Error syncing pod
Normal SandboxChanged Pod sandbox changed, it will be killed and re-created.
Count
列表示这些错误正在一次又一次地重复,大约每秒重复一次。下面是此命令的完整输出,但如何调试此命令?我甚至不知道这些错误是什么意思
Name: ocr-extra-2939512459-3hkv1
Namespace: ocr-da-cluster
Node: gke-da-ocr-api-gce-cluster-extra-pool-65029b63-6qs2/10.240.0.11
Start Time: Tue, 24 Oct 2017 21:05:01 -0400
Labels: component=ocr
pod-template-hash=2939512459
role=extra
Annotations: kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"ReplicaSet","namespace":"ocr-da-cluster","name":"ocr-extra-2939512459","uid":"d58bd050-b8f3-11e7-9f9e-4201...
Status: Pending
IP:
Created By: ReplicaSet/ocr-extra-2939512459
Controlled By: ReplicaSet/ocr-extra-2939512459
Containers:
ocr-node:
Container ID:
Image: us.gcr.io/ocr-api/ocr-image
Image ID:
Ports: 80/TCP, 443/TCP, 5555/TCP, 15672/TCP, 25672/TCP, 4369/TCP, 11211/TCP
State: Waiting
Reason: ContainerCreating
Ready: False
Restart Count: 0
Requests:
cpu: 31
memory: 10Gi
Liveness: http-get http://:http/ocr/live delay=270s timeout=30s period=60s #success=1 #failure=5
Readiness: http-get http://:http/_ah/warmup delay=180s timeout=60s period=120s #success=1 #failure=3
Environment:
NAMESPACE: ocr-da-cluster (v1:metadata.namespace)
Mounts:
/var/log/apache2 from apachelog (rw)
/var/log/celery from cellog (rw)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-dhjr5 (ro)
log-apache2-error:
Container ID:
Image: busybox
Image ID:
Port: <none>
Args:
/bin/sh
-c
echo Apache2 Error && sleep 90 && tail -n+1 -F /var/log/apache2/error.log
State: Waiting
Reason: ContainerCreating
Ready: False
Restart Count: 0
Requests:
cpu: 20m
Environment: <none>
Mounts:
/var/log/apache2 from apachelog (ro)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-dhjr5 (ro)
log-worker-1:
Container ID:
Image: busybox
Image ID:
Port: <none>
Args:
/bin/sh
-c
echo Celery Worker && sleep 90 && tail -n+1 -F /var/log/celery/worker*.log
State: Waiting
Reason: ContainerCreating
Ready: False
Restart Count: 0
Requests:
cpu: 20m
Environment: <none>
Mounts:
/var/log/celery from cellog (ro)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-dhjr5 (ro)
Conditions:
Type Status
Initialized True
Ready False
PodScheduled True
Volumes:
apachelog:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
cellog:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
default-token-dhjr5:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-dhjr5
Optional: false
QoS Class: Burstable
Node-Selectors: beta.kubernetes.io/instance-type=n1-highcpu-32
Tolerations: node.alpha.kubernetes.io/notReady:NoExecute for 300s
node.alpha.kubernetes.io/unreachable:NoExecute for 300s
Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
10m 10m 2 default-scheduler Warning FailedScheduling No nodes are available that match all of the following predicates:: Insufficient cpu (10), Insufficient memory (2), MatchNodeSelector (2).
10m 10m 1 default-scheduler Normal Scheduled Successfully assigned ocr-extra-2939512459-3hkv1 to gke-da-ocr-api-gce-cluster-extra-pool-65029b63-6qs2
10m 10m 1 kubelet, gke-da-ocr-api-gce-cluster-extra-pool-65029b63-6qs2 Normal SuccessfulMountVolume MountVolume.SetUp succeeded for volume "apachelog"
10m 10m 1 kubelet, gke-da-ocr-api-gce-cluster-extra-pool-65029b63-6qs2 Normal SuccessfulMountVolume MountVolume.SetUp succeeded for volume "cellog"
10m 10m 1 kubelet, gke-da-ocr-api-gce-cluster-extra-pool-65029b63-6qs2 Normal SuccessfulMountVolume MountVolume.SetUp succeeded for volume "default-token-dhjr5"
10m 1s 382 kubelet, gke-da-ocr-api-gce-cluster-extra-pool-65029b63-6qs2 Warning FailedSync Error syncing pod
10m 0s 382 kubelet, gke-da-ocr-api-gce-cluster-extra-pool-65029b63-6qs2 Normal SandboxChanged Pod sandbox changed, it will be killed and re-created.
名称:ocr-extra-2939512459-3hkv1
名称空间:ocr da群集
节点:gke-da-ocr-api-gce-cluster-extra-pool-65029b63-6qs2/10.240.0.11
开始时间:2017年10月24日星期二21:05:01-0400
标签:组件=ocr
pod模板哈希=2939512459
角色=额外
注释:kubernetes.io/创建人={“种类”:“序列化引用”,“apiVersion”:“v1”,“引用”:{“种类”:“复制集”,“命名空间”:“ocr da群集”,“名称”:“ocr-extra-2939512459”,“uid”:“d58bd050-b8f3-11e7-9f9e-4201…”。。。
状态:待定
知识产权:
创建人:ReplicaSet/ocr-extra-2939512459
控制人:ReplicaSet/ocr-extra-2939512459
容器:
ocr节点:
容器ID:
图像:us.gcr.io/ocr-api/ocr-Image
图像ID:
端口:80/TCP、443/TCP、5555/TCP、15672/TCP、25672/TCP、4399/TCP、11211/TCP
国家:等待
原因:集装箱制造
就绪:错误
重新启动计数:0
请求:
中央处理器:31
内存:10Gi
活跃度:http get http://:http/ocr/live delay=270s超时=30s周期=60s成功=1失败=5
准备就绪:http get http://:http/_ah/预热延迟=180s超时=60s周期=120s成功=1失败=3
环境:
名称空间:ocr da集群(v1:metadata.NAMESPACE)
挂载:
/来自apachelog(rw)的var/log/apache2
/来自cellog(rw)的var/log/芹菜
/来自default-token-dhjr5(ro)的var/run/secrets/kubernetes.io/servicecomport
log-apache2-error:
容器ID:
图片:busybox
图像ID:
端口:
Args:
/垃圾箱/垃圾箱
-c
echo Apache2 Error&&sleep 90&&tail-n+1-F/var/log/Apache2/Error.log
国家:等待
原因:集装箱制造
就绪:错误
重新启动计数:0
请求:
cpu:20m
环境:
挂载:
/来自apachelog(ro)的var/log/apache2
/来自default-token-dhjr5(ro)的var/run/secrets/kubernetes.io/servicecomport
log-worker-1:
容器ID:
图片:busybox
图像ID:
端口:
Args:
/垃圾箱/垃圾箱
-c
echo芹菜工人和睡眠90和尾部-n+1-F/var/log/芹菜/工人*.log
国家:等待
原因:集装箱制造
就绪:错误
重新启动计数:0
请求:
cpu:20m
环境:
挂载:
/var/log/来自cellog的芹菜(ro)
/来自default-token-dhjr5(ro)的var/run/secrets/kubernetes.io/servicecomport
条件:
类型状态
初始化为True
准备错误
播客预定为真
卷数:
阿帕切洛格:
类型:EmptyDir(共享pod生存期的临时目录)
中等:
赛洛格:
类型:EmptyDir(共享pod生存期的临时目录)
中等:
default-token-dhjr5:
类型:Secret(由Secret填充的卷)
SecretName:default-token-dhjr5
可选:false
QoS等级:Burstable
节点选择器:beta.kubernetes.io/实例类型=n1-highcpu-32
容差:node.alpha.kubernetes.io/notReady:NoExecute持续300秒
node.alpha.kubernetes.io/不可访问:不执行300秒
活动:
子对象路径类型原因消息中的FirstSeen LastSeen计数
--------- -------- ----- ---- ------------- -------- ------ -------
10m 10m 2默认调度程序警告失败调度没有匹配以下所有谓词的可用节点::cpu不足(10)、内存不足(2)、匹配节点选择器(2)。
10m 10m 1默认调度程序正常调度已成功将ocr-extra-2939512459-3hkv1分配给gke-da-ocr-api-gce-cluster-extra-pool-65029b63-6qs2
10m 10m 1 kubelet,gke-da-ocr-api-gce-cluster-extra-pool-65029b63-6qs2正常成功装入卷装入卷。卷“apachelog”的安装成功
10m 10m 1 kubelet,gke-da-ocr-api-gce-cluster-extra-pool-65029b63-6qs2正常成功装入卷装入卷。卷“cellog”的安装成功
10m 10m 1 kubelet,gke-da-ocr-api-gce-cluster-extra-pool-65029b63-6qs2正常成功装入卷装入卷。卷“default-token-dhjr5”的安装成功
10m 1s 382 kubelet,gke-da-ocr-api-gce-cluster-extra-pool-65029b63-6qs2警告同步失败错误同步pod
10m 0s 382 kubelet,gke-da-ocr-api-gce-cluster-extra-pool-65029b63-6qs2普通沙箱已更改Pod沙箱已更改,它将被杀死并重新创建。
检查您的资源限制。我遇到了同样的问题,原因是我使用的是m
而不是Mi