Kubernetes pod状态出现CrashLoopBackOff 的原因
做個(gè)實(shí)驗(yàn):
$ kubectl run crasher --image=rosskukulinski/crashing-app
查看這個(gè)pod的狀態(tài):
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
crasher-2443551393-vuehs 0/1 CrashLoopBackOff 2 54s
CrashLoopBackOff的含義是,Kubernetes試圖啟動(dòng)該P(yáng)od,但是過程中出現(xiàn)錯(cuò)誤,導(dǎo)致容器啟動(dòng)失敗或者正在被刪除。
用describe命令查看明細(xì):
$ kubectl describe pod crasher-2443551393-vuehs
Name: crasher-2443551393-vuehs
Namespace: fail
Node: gke-nrhk-1-default-pool-a101b974-wfp7/10.142.0.2
Start Time: Fri, 10 Feb 2019 14:20:29 -0500
Labels: pod-template-hash=2443551393
run=crasher
Status: Running
IP: 10.0.0.74
Controllers: ReplicaSet/crasher-2443551393
Containers:
crasher:
Container ID: docker://51c940ab32016e6d6b5ed28075357661fef3282cb3569117b0f815a199d01c60
Image: rosskukulinski/crashing-app
Image ID: docker://sha256:cf7452191b34d7797a07403d47a1ccf5254741d4bb356577b8a5de40864653a5
Port:
State: Terminated
Reason: Error
Exit Code: 1
Started: Fri, 10 Feb 2017 14:22:24 -0500
Finished: Fri, 10 Feb 2017 14:22:26 -0500
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Fri, 10 Feb 2017 14:21:39 -0500
Finished: Fri, 10 Feb 2017 14:21:40 -0500
Ready: False
Restart Count: 4
Pod狀態(tài)變?yōu)門erminated,Exit Code 是 1。
查看應(yīng)用日志:
$ kubectl logs crasher-2443551393-vuehs
查看前一個(gè)容器:
$ kubectl logs crasher-2443551393-vuehs --previous
要獲取更多Jerry的原創(chuàng)文章,請(qǐng)關(guān)注公眾號(hào)"汪子熙":
總結(jié)
以上是生活随笔為你收集整理的Kubernetes pod状态出现CrashLoopBackOff 的原因的全部內(nèi)容,希望文章能夠幫你解決所遇到的問題。
- 上一篇: 华为6+128和8+128区别
- 下一篇: 华为p30pro 原厂带钢化膜吗