From f845902087c7773b8580224ba71d1ce07f823cf6 Mon Sep 17 00:00:00 2001 From: "Lubomir I. Ivanov" Date: Fri, 18 May 2018 20:15:53 +0300 Subject: [PATCH] troubleshooting-kubeadm: add note about kubeadm-reset block (#8508) Add note about a possible block when calling 'kubeadm reset' if the Docker service refuses to remove the k8s managed containers. --- .../independent/troubleshooting-kubeadm.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/content/en/docs/setup/independent/troubleshooting-kubeadm.md b/content/en/docs/setup/independent/troubleshooting-kubeadm.md index 16c393f846..db916c2506 100644 --- a/content/en/docs/setup/independent/troubleshooting-kubeadm.md +++ b/content/en/docs/setup/independent/troubleshooting-kubeadm.md @@ -73,6 +73,24 @@ kubectl -n ${NAMESPACE} logs ${POD_NAME} -c ${CONTAINER_NAME} - control plane Docker containers are crashlooping or hanging. You can check this by running `docker ps` and investigating each container by running `docker logs`. +#### kubeadm blocks when removing managed containers + +The following could happen if Docker halts and does not remove any Kubernetes-managed containers: + +```bash +sudo kubeadm reset +[preflight] Running pre-flight checks +[reset] Stopping the kubelet service +[reset] Unmounting mounted directories in "/var/lib/kubelet" +[reset] Removing kubernetes-managed containers +(block) +``` + +A possible solution is to restart the Docker service and then re-run `kubeadm reset`: +```bash +sudo systemctl restart docker.service +sudo kubeadm reset +``` #### Pods in `RunContainerError`, `CrashLoopBackOff` or `Error` state