kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Add diagnose tips when you face problem.

pull/2634/head
huzhifeng 2017-02-26 11:39:46 +08:00 committed by Andrew Chen
parent 11f3e0fec1
commit d30c4a7c78
1 changed files with 32 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
docs/getting-started-guides/kubeadm.md
View File

@ -195,6 +195,38 @@ Once a pod network has been installed, you can confirm that it is working by che
And once the `kube-dns` pod is up and running, you can continue by joining your nodes. And once the `kube-dns` pod is up and running, you can continue by joining your nodes.
If you see following status
```
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system canal-node-f0lqp 2/3 RunContainerError 2 48s
```
Or
```
kube-system canal-node-77d0h 2/3 CrashLoopBackOff 3 3m
kube-system kube-dns-2924299975-7q1vq 0/4 ContainerCreating 0 15m
```
The three status ```RunContainerError``` and ```CrashLoopBackOff``` and ```ContainerCreating``` very common.
You may have trouble in configure. to diagnose what happened. you can using ```kubectl describe -n kube-system po {YOUR_POD_NAME}``` to check what's in logs. do not using kubectl logs. you will got
```
# kubectl logs -n kube-system canal-node-f0lqp
Error from server (BadRequest): the server rejected our request for an unknown reason (get pods canal-node-f0lqp)
```
The kubectl describe will gave you more details about the logs
```
# kubectl describe -n kube-system po kube-dns-2924299975-1l2t7
2m 2m 1 {kubelet nac} spec.containers{flannel} Warning Failed Failed to start container with docker id 927e7ccdc32b with error: Error response from daemon: {"message":"chown /etc/resolv.conf: operation not permitted"}
```
Or
```
6m 1m 191 {kubelet nac} Warning FailedSync Error syncing pod, skipping: failed to "SetupNetwork" for "kube-dns-2924299975-1l2t7_kube-system" with SetupNetworkError: "Failed to setup network for pod \"kube-dns-2924299975-1l2t7_kube-system(dee8ef21-fbcb-11e6-ba19-38d547e0006a)\" using network plugins \"cni\": open /run/flannel/subnet.env: no such file or directory; Skipping pod"
```
Then you can do some search with google, and you will find solutions.
### (4/4) Joining your nodes ### (4/4) Joining your nodes
The nodes are where your workloads (containers and pods, etc) run. The nodes are where your workloads (containers and pods, etc) run.