opened
kharisj
username_0
I'm new for kubernetes and I choose canal for my kubernetes network.
I struck with this error for a week and I cannot bring kube-dns up. For more information I try to compare with weave network. in my kubernetes with weave was succesful and I hope canal will be more powerful than weave. error as following

```
[root@master ~]# kubectl get po --all-namespaces
NAMESPACE     NAME                                   READY     STATUS              RESTARTS   AGE
kube-system   calico-etcd-2r5k6                      0/1       CrashLoopBackOff    5          3m
kube-system   calico-node-nbad7                      1/2       Error               4          3m
kube-system   calico-node-sj2z5                      1/2       Error               2          3m
kube-system   calico-policy-controller-snp8a         0/1       CrashLoopBackOff    3          3m
kube-system   configure-calico-jqp0m                 0/1       CrashLoopBackOff    2          3m
kube-system   etcd-master.local                      1/1       Running             0          6m
kube-system   kube-apiserver-master.local            1/1       Running             0          6m
kube-system   kube-controller-manager-master.local   1/1       Running             0          8m
kube-system   kube-discovery-982812725-dhbby         1/1       Running             0          8m
kube-system   kube-dns-2247936740-89ob1              0/3       ContainerCreating   0          7m
kube-system   kube-proxy-amd64-ib9ct                 1/1       Running             0          7m
kube-system   kube-proxy-amd64-rn4r9                 1/1       Running             0          7m
kube-system   kube-scheduler-master.local            1/1       Running             0          7m
```

[canal.txt](https://github.com/projectcalico/calico-containers/files/538674/canal.txt)
All canal container  CrashLoopBackOff with default kubeadm initialize
issue
created
xiaochunyn
username_1
@username_0 Disabling SELinux by running "setenforce 0" is required in order to allow containers to access the host filesystem.
comment