github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-06 02:34:03 +00:00
Code Issues Projects Releases Wiki Activity

kubeadm-init: update note about failing containers

Browse Source 
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
This commit is contained in:
Lubomir I. Ivanov 2018-05-12 02:26:10 +03:00
parent 5782d476c5
commit af44aa1491
1 changed files with 7 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
cmd/kubeadm/app/cmd/init.go
View File

@ -104,13 +104,12 @@ var (
- 'systemctl status kubelet' - 'systemctl status kubelet'
- 'journalctl -xeu kubelet' - 'journalctl -xeu kubelet'
Additionally a control plane component may not have come up in docker. If that's the case, you can enumerate Additionally, a control plane component may have crashed or exited when started by the container runtime.
all docker containers that have been started (including ones that have crashed and exited) by running the To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker.
following commands: Here is one example how you may list all Kubernetes containers running in docker:
- 'docker ps -a' - 'docker ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
Once you have that list, you can inspect the logs for any pod with: - 'docker logs CONTAINERID'
- 'docker logs $CONTAINERID'
`))) `)))
) )