From af44aa1491b11929bbc5963f4f4a37a438616c5e Mon Sep 17 00:00:00 2001 From: "Lubomir I. Ivanov" Date: Sat, 12 May 2018 02:26:10 +0300 Subject: [PATCH] kubeadm-init: update note about failing containers This PR was merged before all requested changes were applied: kubernetes/pull/59731 Update the note about failing containers as requested here: https://github.com/kubernetes/kubernetes/pull/59731#pullrequestreview-119517427 --- cmd/kubeadm/app/cmd/init.go | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/cmd/kubeadm/app/cmd/init.go b/cmd/kubeadm/app/cmd/init.go index d77f30e7765..3ca2935941b 100644 --- a/cmd/kubeadm/app/cmd/init.go +++ b/cmd/kubeadm/app/cmd/init.go @@ -103,14 +103,13 @@ var ( If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands: - 'systemctl status kubelet' - 'journalctl -xeu kubelet' - - Additionally a control plane component may not have come up in docker. If that's the case, you can enumerate - all docker containers that have been started (including ones that have crashed and exited) by running the - following commands: - - 'docker ps -a' - - Once you have that list, you can inspect the logs for any pod with: - - 'docker logs $CONTAINERID' + + Additionally, a control plane component may have crashed or exited when started by the container runtime. + To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker. + Here is one example how you may list all Kubernetes containers running in docker: + - 'docker ps -a | grep kube | grep -v pause' + Once you have found the failing container, you can inspect its logs with: + - 'docker logs CONTAINERID' `))) )