whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

troubleshooting-kubeadm: add note about kubeadm-reset block (#8508)

Browse Source 
Add note about a possible block when calling 'kubeadm reset'
if the Docker service refuses to remove the k8s managed containers.
This commit is contained in:
Lubomir I. Ivanov
2018-05-18 20:15:53 +03:00
committed by k8s-ci-robot
parent 3f403d5dc3
commit f845902087
1 changed files with 18 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/setup/independent/troubleshooting-kubeadm.md
+18
View File
@@ -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`. - 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 #### Pods in `RunContainerError`, `CrashLoopBackOff` or `Error` state