Kubernetes Pod 因 CrashLoopBackOff 而失敗
[英]Kubernetes Pod fails with CrashLoopBackOff
問題描述
我正在按照本指南使用 minikube 設置一個 pod 並從托管在以下位置的私有存儲庫中提取圖像： hub.docker.com
嘗試設置 pod 以拉取圖像時，我看到CrashLoopBackoff
吊艙配置：
apiVersion: v1
kind: Pod
metadata:
name: private-reg
spec:
containers:
- name: private-reg-container
image: ha/prod:latest
imagePullSecrets:
- name: regsecret
“獲取吊艙”的輸出
kubectl get pod private-reg
NAME READY STATUS RESTARTS AGE
private-reg 0/1 CrashLoopBackOff 5 4m
據我所知，圖像沒有問題，如果我手動拉動它們並運行它們，它們就可以工作。
（你可以看到Successfully pulled image "ha/prod:latest" ）
如果我將通用映像推送到存儲庫（例如 centos）並嘗試使用 pod 拉取和運行它，也會發生此問題。
此外，這個秘密似乎工作正常，我可以看到私有存儲庫中計算的“拉動”。
這是命令的輸出：
kubectl describe pods private-reg ：
[~]$ kubectl describe pods private-reg
Name: private-reg
Namespace: default
Node: minikube/192.168.99.100
Start Time: Thu, 22 Jun 2017 17:13:24 +0300
Labels: <none>
Annotations: <none>
Status: Running
IP: 172.17.0.5
Controllers: <none>
Containers:
private-reg-container:
Container ID: docker://1aad64750d0ba9ba826fe4f12c8814f7db77293078f8047feec686fcd8f90132
Image: ha/prod:latest
Image ID: docker://sha256:7335859e2071af518bcd0e2f373f57c1da643bb37c7e6bbc125d171ff98f71c0
Port:
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Completed
Exit Code: 0
Started: Mon, 01 Jan 0001 00:00:00 +0000
Finished: Thu, 22 Jun 2017 17:20:04 +0300
Ready: False
Restart Count: 6
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-bhvgz (ro)
Conditions:
Type Status
Initialized True
Ready False
PodScheduled True
Volumes:
default-token-bhvgz:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-bhvgz
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: <none>
Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
9m 9m 1 default-scheduler Normal Scheduled Successfully assigned private-reg to minikube
8m 8m 1 kubelet, minikube spec.containers{private-reg-container} Normal Created Created container with id 431fecfd1d2ca03d29fd88fd6c663e66afb59dc5e86487409002dd8e9987945c
8m 8m 1 kubelet, minikube spec.containers{private-reg-container} Normal Started Started container with id 431fecfd1d2ca03d29fd88fd6c663e66afb59dc5e86487409002dd8e9987945c
8m 8m 1 kubelet, minikube spec.containers{private-reg-container} Normal Started Started container with id 223e6af99bb950570a27056d7401137ff9f3dc895f4f313a36e73ef6489eb61a
8m 8m 1 kubelet, minikube spec.containers{private-reg-container} Normal Created Created container with id 223e6af99bb950570a27056d7401137ff9f3dc895f4f313a36e73ef6489eb61a
8m 8m 2 kubelet, minikube Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "private-reg-container" with CrashLoopBackOff: "Back-off 10s restarting failed container=private-reg-container pod=private-reg_default(f4340638-5754-11e7-978a-08002773375c)"
8m 8m 1 kubelet, minikube spec.containers{private-reg-container} Normal Started Started container with id a98377f9aedc5947fe1dd006caddb11fb48fa2fd0bb06c20667e0c8b83a3ab6a
8m 8m 1 kubelet, minikube spec.containers{private-reg-container} Normal Created Created container with id a98377f9aedc5947fe1dd006caddb11fb48fa2fd0bb06c20667e0c8b83a3ab6a
8m 8m 2 kubelet, minikube Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "private-reg-container" with CrashLoopBackOff: "Back-off 20s restarting failed container=private-reg-container pod=private-reg_default(f4340638-5754-11e7-978a-08002773375c)"
8m 8m 1 kubelet, minikube spec.containers{private-reg-container} Normal Started Started container with id 261f430a80ff5a312bdbdee78558091a9ae7bc9fc6a9e0676207922f1a576841
8m 8m 1 kubelet, minikube spec.containers{private-reg-container} Normal Created Created container with id 261f430a80ff5a312bdbdee78558091a9ae7bc9fc6a9e0676207922f1a576841
8m 7m 3 kubelet, minikube Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "private-reg-container" with CrashLoopBackOff: "Back-off 40s restarting failed container=private-reg-container pod=private-reg_default(f4340638-5754-11e7-978a-08002773375c)"
7m 7m 1 kubelet, minikube spec.containers{private-reg-container} Normal Created Created container with id 7251ab76853d4178eff59c10bb41e52b2b1939fbee26e546cd564e2f6b4a1478
7m 7m 1 kubelet, minikube spec.containers{private-reg-container} Normal Started Started container with id 7251ab76853d4178eff59c10bb41e52b2b1939fbee26e546cd564e2f6b4a1478
7m 5m 7 kubelet, minikube Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "private-reg-container" with CrashLoopBackOff: "Back-off 1m20s restarting failed container=private-reg-container pod=private-reg_default(f4340638-5754-11e7-978a-08002773375c)"
5m 5m 1 kubelet, minikube spec.containers{private-reg-container} Normal Created Created container with id 347868d03fc9730417cf234e4c96195bb9b45a6cc9d9d97973855801d52e2a02
5m 5m 1 kubelet, minikube spec.containers{private-reg-container} Normal Started Started container with id 347868d03fc9730417cf234e4c96195bb9b45a6cc9d9d97973855801d52e2a02
5m 3m 12 kubelet, minikube Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "private-reg-container" with CrashLoopBackOff: "Back-off 2m40s restarting failed container=private-reg-container pod=private-reg_default(f4340638-5754-11e7-978a-08002773375c)"
9m 2m 7 kubelet, minikube spec.containers{private-reg-container} Normal Pulling pulling image "ha/prod:latest"
2m 2m 1 kubelet, minikube spec.containers{private-reg-container} Normal Started Started container with id 1aad64750d0ba9ba826fe4f12c8814f7db77293078f8047feec686fcd8f90132
8m 2m 7 kubelet, minikube spec.containers{private-reg-container} Normal Pulled Successfully pulled image "ha/prod:latest"
2m 2m 1 kubelet, minikube spec.containers{private-reg-container} Normal Created Created container with id 1aad64750d0ba9ba826fe4f12c8814f7db77293078f8047feec686fcd8f90132
8m <invalid> 40 kubelet, minikube spec.containers{private-reg-container} Warning BackOff Back-off restarting failed container
2m <invalid> 14 kubelet, minikube Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "private-reg-container" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=private-reg-container pod=private-reg_default(f4340638-5754-11e7-978a-08002773375c)"
這是命令的輸出：
kubectl --v=8 logs private-reg ：
I0622 17:35:01.043739 15981 cached_discovery.go:71] returning cached discovery info from /home/demo/.kube/cache/discovery/192.168.99.100_8443/apps/v1beta1/serverresources.json
I0622 17:35:01.043951 15981 cached_discovery.go:71] returning cached discovery info from /home/demo/.kube/cache/discovery/192.168.99.100_8443/v1/serverresources.json
I0622 17:35:01.045061 15981 cached_discovery.go:118] returning cached discovery info from /home/demo/.kube/cache/discovery/192.168.99.100_8443/servergroups.json
I0622 17:35:01.045175 15981 round_trippers.go:395] GET https://192.168.99.100:8443/api/v1/namespaces/default/pods/private-reg
I0622 17:35:01.045182 15981 round_trippers.go:402] Request Headers:
I0622 17:35:01.045187 15981 round_trippers.go:405] Accept: application/json, */*
I0622 17:35:01.045191 15981 round_trippers.go:405] User-Agent: kubectl/v1.6.6 (linux/amd64) kubernetes/7fa1c17
I0622 17:35:01.072863 15981 round_trippers.go:420] Response Status: 200 OK in 27 milliseconds
I0622 17:35:01.072900 15981 round_trippers.go:423] Response Headers:
I0622 17:35:01.072921 15981 round_trippers.go:426] Content-Type: application/json
I0622 17:35:01.072930 15981 round_trippers.go:426] Content-Length: 2216
I0622 17:35:01.072936 15981 round_trippers.go:426] Date: Thu, 22 Jun 2017 14:35:31 GMT
I0622 17:35:01.072994 15981 request.go:991] Response Body: {"kind":"Pod","apiVersion":"v1","metadata":{"name":"private-reg","namespace":"default","selfLink":"/api/v1/namespaces/default/pods/private-reg","uid":"f4340638-5754-11e7-978a-08002773375c","resourceVersion":"3070","creationTimestamp":"2017-06-22T14:13:24Z"},"spec":{"volumes":[{"name":"default-token-bhvgz","secret":{"secretName":"default-token-bhvgz","defaultMode":420}}],"containers":[{"name":"private-reg-container","image":"ha/prod:latest","resources":{},"volumeMounts":[{"name":"default-token-bhvgz","readOnly":true,"mountPath":"/var/run/secrets/kubernetes.io/serviceaccount"}],"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","imagePullPolicy":"Always"}],"restartPolicy":"Always","terminationGracePeriodSeconds":30,"dnsPolicy":"ClusterFirst","serviceAccountName":"default","serviceAccount":"default","nodeName":"minikube","securityContext":{},"imagePullSecrets":[{"name":"regsecret"}],"schedulerName":"default-scheduler"},"status":{"phase":"Running","conditions":[{"type":"Initialized","status":"True","lastProbeTime":null,"lastTransitionTime":"2017-06-22T14:13:24Z"},{"type":"Ready","status":"False","lastProbeTime":null,"lastTransitionTime":"2017-06-22T14:13:24Z","reason":"ContainersNotReady","message":"containers with unready status: [private-reg-container]"},{"type":"PodScheduled","status":"True","lastProbeTime":null,"lastTransitionTime":"2017-06-22T14:13:24Z"}],"hostIP":"192.168.99.100","podIP":"172.17.0.5","startTime":"2017-06-22T14:13:24Z","containerStatuses":[{"name":"private-reg-container","state":{"waiting":{"reason":"CrashLoopBackOff","message":"Back-off 5m0s restarting failed container=private-reg-container pod=private-reg_default(f4340638-5754-11e7-978a-08002773375c)"}},"lastState":{"terminated":{"exitCode":0,"reason":"Completed","startedAt":null,"finishedAt":"2017-06-22T14:30:36Z","containerID":"docker://a4cb436a79b0b21bb385e544d424b2444a80ca66160ef21af30ab69ed2e23b32"}},"ready":false,"restartCount":8,"image":"ha/prod:latest","imageID":"docker://sha256:7335859e2071af518bcd0e2f373f57c1da643bb37c7e6bbc125d171ff98f71c0","containerID":"docker://a4cb436a79b0b21bb385e544d424b2444a80ca66160ef21af30ab69ed2e23b32"}],"qosClass":"BestEffort"}}
I0622 17:35:01.074108 15981 round_trippers.go:395] GET https://192.168.99.100:8443/api/v1/namespaces/default/pods/private-reg/log
I0622 17:35:01.074126 15981 round_trippers.go:402] Request Headers:
I0622 17:35:01.074132 15981 round_trippers.go:405] Accept: application/json, */*
I0622 17:35:01.074137 15981 round_trippers.go:405] User-Agent: kubectl/v1.6.6 (linux/amd64) kubernetes/7fa1c17
I0622 17:35:01.079257 15981 round_trippers.go:420] Response Status: 200 OK in 5 milliseconds
I0622 17:35:01.079289 15981 round_trippers.go:423] Response Headers:
I0622 17:35:01.079299 15981 round_trippers.go:426] Content-Type: text/plain
I0622 17:35:01.079307 15981 round_trippers.go:426] Content-Length: 0
I0622 17:35:01.079315 15981 round_trippers.go:426] Date: Thu, 22 Jun 2017 14:35:31 GMT
我該如何調試這個問題？
更新
輸出：
kubectl --v=8 logs ps-agent-2028336249-3pk43 --namespace=default -p
I0625 11:30:01.569903 13420 round_trippers.go:395] GET
I0625 11:30:01.569920 13420 round_trippers.go:402] Request Headers:
I0625 11:30:01.569927 13420 round_trippers.go:405] User-Agent: kubectl/v1.6.6 (linux/amd64) kubernetes/7fa1c17
I0625 11:30:01.569934 13420 round_trippers.go:405] Accept: application/json, */*
I0625 11:30:01.599026 13420 round_trippers.go:420] Response Status: 200 OK in 29 milliseconds
I0625 11:30:01.599048 13420 round_trippers.go:423] Response Headers:
I0625 11:30:01.599056 13420 round_trippers.go:426] Date: Sun, 25 Jun 2017 08:30:01 GMT
I0625 11:30:01.599062 13420 round_trippers.go:426] Content-Type: application/json
I0625 11:30:01.599069 13420 round_trippers.go:426] Content-Length: 2794
I0625 11:30:01.599264 13420 request.go:991] Response Body: {"kind":"Pod","apiVersion":"v1","metadata":{"name":"ps-agent-2028336249-3pk43","generateName":"ps-agent-2028336249-","namespace":"default","selfLink":"/api/v1/namespaces/default/pods/ps-agent-2028336249-3pk43","uid":"87c69072-597e-11e7-83cd-08002773375c","resourceVersion":"14354","creationTimestamp":"2017-06-25T08:16:03Z","labels":{"pod-template-hash":"2028336249","run":"ps-agent"},"annotations":{"kubernetes.io/created-by":"{\"kind\":\"SerializedReference\",\"apiVersion\":\"v1\",\"reference\":{\"kind\":\"ReplicaSet\",\"namespace\":\"default\",\"name\":\"ps-agent-2028336249\",\"uid\":\"87c577b5-597e-11e7-83cd-08002773375c\",\"apiVersion\":\"extensions\",\"resourceVersion\":\"13446\"}}\n"},"ownerReferences":[{"apiVersion":"extensions/v1beta1","kind":"ReplicaSet","name":"ps-agent-2028336249","uid":"87c577b5-597e-11e7-83cd-08002773375c","controller":true,"blockOwnerDeletion":true}]},"spec":{"volumes":[{"name":"default-token-bhvgz","secret":{"secretName":"default-token-bhvgz","defaultMode":420}}],"containers":[{"name":"ps-agent","image":"ha/prod:ps-agent-latest","resources":{},"volumeMounts":[{"name":"default-token-bhvgz","readOnly":true,"mountPath":"/var/run/secrets/kubernetes.io/serviceaccount"}],"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","imagePullPolicy":"IfNotPresent"}],"restartPolicy":"Always","terminationGracePeriodSeconds":30,"dnsPolicy":"ClusterFirst","serviceAccountName":"default","serviceAccount":"default","nodeName":"minikube","securityContext":{},"schedulerName":"default-scheduler"},"status":{"phase":"Running","conditions":[{"type":"Initialized","status":"True","lastProbeTime":null,"lastTransitionTime":"2017-06-25T08:16:03Z"},{"type":"Ready","status":"False","lastProbeTime":null,"lastTransitionTime":"2017-06-25T08:16:03Z","reason":"ContainersNotReady","message":"containers with unready status: [ps-agent]"},{"type":"PodScheduled","status":"True","lastProbeTime":null,"lastTransitionTime":"2017-06-25T08:16:03Z"}],"hostIP":"192.168.99.100","podIP":"172.17.0.5","startTime":"2017-06-25T08:16:03Z","containerStatuses":[{"name":"ps-agent","state":{"waiting":{"reason":"CrashLoopBackOff","message":"Back-off 5m0s restarting failed container=ps-agent pod=ps-agent-2028336249-3pk43_default(87c69072-597e-11e7-83cd-08002773375c)"}},"lastState":{"terminated":{"exitCode":0,"reason":"Completed","startedAt":null,"finishedAt":"2017-06-25T08:27:17Z","containerID":"docker://1aa9dfbfeb80042c6f4c8d04cabb3306ac1cd52963568e621019e2f1f0ee081b"}},"ready":false,"restartCount":7,"image":"ha/prod:ps-agent-latest","imageID":"docker://sha256:eb5307c4366fc129d022703625a5f30ff175b5e1a24dbe39fd4c32e726a0ee7b","containerID":"docker://1aa9dfbfeb80042c6f4c8d04cabb3306ac1cd52963568e621019e2f1f0ee081b"}],"qosClass":"BestEffort"}}
I0625 11:30:01.600727 13420 round_trippers.go:395] GET https://192.168.99.100:8443/api/v1/namespaces/default/pods/ps-agent-2028336249-3pk43/log?previous=true
I0625 11:30:01.600747 13420 round_trippers.go:402] Request Headers:
I0625 11:30:01.600757 13420 round_trippers.go:405] Accept: application/json, */*
I0625 11:30:01.600766 13420 round_trippers.go:405] User-Agent: kubectl/v1.6.6 (linux/amd64) kubernetes/7fa1c17
I0625 11:30:01.632473 13420 round_trippers.go:420] Response Status: 200 OK in 31 milliseconds
I0625 11:30:01.632545 13420 round_trippers.go:423] Response Headers:
I0625 11:30:01.632569 13420 round_trippers.go:426] Date: Sun, 25 Jun 2017 08:30:01 GMT
I0625 11:30:01.632592 13420 round_trippers.go:426] Content-Type: text/plain
I0625 11:30:01.632615 13420 round_trippers.go:426] Content-Length: 0
6 個解決方案
解決方案1
30 2017-06-25 12:57:52
由 docker 容器導致的問題，該容器在“啟動”過程完成后立即退出。 我添加了一個永遠運行的命令並且它起作用了。 這個問題提到這里
解決方案2
3 2019-01-16 11:08:50
我遇到了同樣的錯誤。
NAME READY STATUS RESTARTS AGE pod/webapp 0/1 CrashLoopBackOff 5 47h
我的問題是我試圖運行兩個具有相同元數據名稱的不同 pod。
種類：Pod 元數據：名稱：webapp 標簽：...
要查找 pod 的所有名稱，請運行：kubectl get pods
NAME READY STATUS RESTARTS AGE webapp 1/1 Running 15 47h
然后我更改了沖突的 pod 名稱，一切正常。
NAME READY STATUS RESTARTS AGE webapp 1/1 Running 17 2d webapp-release-0-5 1/1 Running 0 13m
解決方案3
3 2019-02-12 15:39:24
當我調試獲取 pod 和 pod 日志時，我遇到了類似的問題“CrashLoopBackOff”。 發現我的命令參數是錯誤的
解決方案4
2 2020-01-14 20:23:48
由於 POD 初始化后出現問題，Pod 未啟動。
檢查並使用命令獲取 pod 的 docker 容器
docker ps -a | grep private-reg
輸出將是帶有 id 的 docker 容器的信息。
查看 docker 日志：
docker logs -f <container id>
解決方案5
1 2021-04-07 09:42:01
此處描述並解決了問題https://docs.pivotal.io/tkgi/1-10/velero-install.html 。 需要正確設置主機路徑。
解決方案6
0 2020-01-14 11:24:41
我有類似的情況。 我發現我的配置映射之一被復制了。 我有兩個用於同一個命名空間的配置映射。 一個有正確的命名空間引用，另一個指向錯誤的命名空間。
我刪除並使用正確的文件（或固定文件）重新創建了配置映射。 我只使用一個，這似乎讓特定的集群更快樂。
因此，我會檢查文件中是否有任何可能導致沖突的拼寫錯誤或重復項。
Apache 服務器以 docker 運行，但 kube.netes pod 因 CrashLoopBackOff 而失敗
[英]Apache server runs with docker run but kubernetes pod fails with CrashLoopBackOff
Kubernetes中Pod上的CrashloopBackOff（在具有Jenkins的GCP上）
[英]CrashloopBackOff on Pod in Kubernetes(on GCP with Jenkins)
帶有 React 應用程序的 pod 在 kube.netes 上失敗，狀態為 CrashLoopBackOff
[英]pod with React app failing with with status CrashLoopBackOff on kubernetes
kubernetes pod crashloopbackoff 當 python 腳本在 pod 中執行時
[英]kubernetes pod crashloopbackoff when python script execute in pod
聲明:本站的技術帖子網頁，遵循CC BY-SA 4.0協議，如果您需要轉載，請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.
相關問題
Kubernetes pod 在 crashloopbackoff
Kubernetes Pod 卡在 CrashLoopBackOff 中
Apache 服務器以 docker 運行，但 kube.netes pod 因 CrashLoopBackOff 而失敗
Kubernetes中Pod上的CrashloopBackOff（在具有Jenkins的GCP上）
AKS Pod CrashLoopBackOff 上的 Helm kubernetes
Kubernetes pod 無法啟動並獲得 CrashLoopBackOff
我收到Pod錯誤：來自kubernetes的CrashLoopBackOff
帶有 React 應用程序的 pod 在 kube.netes 上失敗，狀態為 CrashLoopBackOff
kubernetes pod crashloopbackoff 當 python 腳本在 pod 中執行時
Kubernetes容器失敗並給出CrashLoopBackOff錯誤
相關標簽