找到被Minikube殺死的豆莢的原因

我在VirtualBox的本地機器上創建了一個Minikube實例。我有兩個複製控制器爲它們指定了資源限制。首先，我爲每個複製控制器A和B創建一個實例。然後，我將rc B的複製計數增加到6.一旦擴展，我可以看到由rc A創建的Pod被Kubernetes殺死。只有登錄我能在kubeclt日誌中看到是找到被Minikube殺死的豆莢的原因

/opt/app-server/bin/app-server.sh: line 159: 28 Killed     $JAVA_HOME/bin/java -server $JVM_OPTS $XDEBUG $SERVER_OPTS -Djava.endorsed.dirs=$SERVER_ENDORSED -classpath $SERVER_CLASSPATH org.adroitlogic.appserver.AppServer

我不知道是什麼原因導致這種吊艙的驅逐。我猜這與虛擬機上的資源分配和有限的資源有關。但我需要確認。我在哪裏可以找到與拆除此吊艙的原因有關的日誌？我搜索在journalctl -u localkube

Jan 09 11:00:55 minikube localkube[3421]: I0109 11:00:55.136114 3421 docker_manager.go:2524] checking backoff for container "ipsweb" in pod "ipsweb-m3234" 
Jan 09 11:00:55 minikube localkube[3421]: I0109 11:00:55.136525 3421 docker_manager.go:2538] Back-off 5m0s restarting failed container=ipsweb pod=ipsweb-m3234_default(e6961157-d650-11e6-8bee-080027bc9720) 
Jan 09 11:00:55 minikube localkube[3421]: E0109 11:00:55.136571 3421 pod_workers.go:184] Error syncing pod e6961157-d650-11e6-8bee-080027bc9720, skipping: failed to "StartContainer" for "ipsweb" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=ipsweb pod=ipsweb-m3234_default(e6961157-d650-11e6-8bee-080027bc9720)"

kubectl描述莢給出以下事件

Events: 
    FirstSeen LastSeen Count From   SubobjectPath  Type  Reason  Message 
    --------- -------- ----- ----   -------------  -------- ------  ------- 
    1h  1h  1 {kubelet minikube} spec.containers{ipsweb} Normal  Started  Started container with docker id 2ca5ccaa11a1 
    1h  1h  1 {kubelet minikube} spec.containers{ipsweb} Normal  Created  Created container with docker id 2ca5ccaa11a1; Security:[seccomp=unconfined] 
    1h  1h  1 {kubelet minikube} spec.containers{ipsweb} Normal  Started  Started container with docker id 86d4bdfa014e 
    1h  1h  1 {kubelet minikube} spec.containers{ipsweb} Normal  Created  Created container with docker id 86d4bdfa014e; Security:[seccomp=unconfined] 
    50m  50m  1 {kubelet minikube} spec.containers{ipsweb} Normal  Started  Started container with docker id a570e4f59e96 
    50m  50m  1 {kubelet minikube} spec.containers{ipsweb} Normal  Created  Created container with docker id a570e4f59e96; Security:[seccomp=unconfined] 
    1h  49m  2 {kubelet minikube}    Warning  FailedSync Error syncing pod, skipping: failed to "StartContainer" for "ipsweb" with CrashLoopBackOff: "Back-off 10s restarting failed container=ipsweb pod=ipsweb-m3234_default(e6961157-d650-11e6-8bee-080027bc9720)" 

    49m 49m 1 {kubelet minikube} spec.containers{ipsweb} Normal Started  Started container with docker id b91cc20a8bb3 
    49m 49m 1 {kubelet minikube} spec.containers{ipsweb} Normal Created  Created container with docker id b91cc20a8bb3; Security:[seccomp=unconfined] 
    1h 48m 4 {kubelet minikube}    Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "ipsweb" with CrashLoopBackOff: "Back-off 20s restarting failed container=ipsweb pod=ipsweb-m3234_default(e6961157-d650-11e6-8bee-080027bc9720)" 

    48m 48m 1 {kubelet minikube} spec.containers{ipsweb} Normal Started  Started container with docker id cf24faa31718 
    48m 48m 1 {kubelet minikube} spec.containers{ipsweb} Normal Created  Created container with docker id cf24faa31718; Security:[seccomp=unconfined] 
    1h 46m 7 {kubelet minikube}    Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "ipsweb" with CrashLoopBackOff: "Back-off 40s restarting failed container=ipsweb pod=ipsweb-m3234_default(e6961157-d650-11e6-8bee-080027bc9720)"

但上述非給我一個大概的原因和爲什麼發生這種情況提示。任何建議？

來源

2017-01-09 Dimuthu

所以我不知道什麼是正確的做法，但這是我做什麼時，k8s不能給我足夠的信息。

最簡單的方法是查看該吊艙的docker logs。我看到某個吊艙一次又一次地失敗。所以我會轉到minikube機器上並運行

docker ps -a | grep 'some_identifiable_name'

這是我得到的容器ID。一旦我有，我得到該吊艙的日誌。

docker logs <id_found_above>

這應該是辦得這麼快，因爲K8S可能垃圾收集容器之前，你甚至可以執行所有上述步驟。

來源

2017-04-04 05:19:58 surajd

要獲得簡單的方式，每個吊艙，運行以下命令的日誌，

$ minikube dashboard

然後kubernetes儀表板將在瀏覽器中打開。然後轉到Pods，在容器選項卡下，將出現選項View logs，您可以從中實際看到容器內部發生了什麼或者爲什麼它失敗

來源

2017-04-11 08:50:27

找到被Minikube殺死的豆莢的原因

回答

相關問題