kubeadm with output from pre-pulling docker images

gistfile1.txt

(root@centos1 ~) $ systemctl stop docker
(root@centos1 ~) $ kubeadm init master
<master/tokens> generated token: "c577ff.b591499b65f33385"
I1001 15:25:37.644317   12621 docker.go:324] Connecting to docker on unix:///var/run/docker.sock
I1001 15:25:37.644383   12621 docker.go:344] Start docker client with request timeout=10s
E1001 15:25:37.644557   12621 kube_docker_client.go:98] failed to retrieve docker version: Cannot connect to the Docker daemon. Is the docker daemon running on this host?
W1001 15:25:37.644564   12621 kube_docker_client.go:99] Using empty version for docker client, this may sometimes cause compatibility issue.
error: Cannot connect to the Docker daemon. Is the docker daemon running on this host?
(root@centos1 ~) $ systemctl start docker
(root@centos1 ~) $           
(root@centos1 ~) $ 
(root@centos1 ~) $ systemctl start kubelet
(root@centos1 ~) $ 
(root@centos1 ~) $ 
(root@centos1 ~) $ ls
anaconda-ks.cfg  reset.sh*
(root@centos1 ~) $ kubeadm init master
<master/tokens> generated token: "d38a9c.cd3ce1cd7f932db5"
I1001 15:32:37.327214   12791 docker.go:324] Connecting to docker on unix:///var/run/docker.sock
I1001 15:32:37.327338   12791 docker.go:344] Start docker client with request timeout=10s
<images/images> Pulling image: gcr.io/google_containers/kube-apiserver-amd64:v1.4.0
<images/images> Pulling image: gcr.io/google_containers/kube-controller-manager-amd64:v1.4.0
<images/images> Pulling image: gcr.io/google_containers/kube-scheduler-amd64:v1.4.0
<images/images> Pulling image: gcr.io/google_containers/kube-discovery-amd64:1.0
<images/images> Pulling image: gcr.io/google_containers/etcd-amd64:2.2.5
<master/pki> created keys and certificates in "/etc/kubernetes/pki"
<util/kubeconfig> created "/etc/kubernetes/kubelet.conf"
<util/kubeconfig> created "/etc/kubernetes/admin.conf"
<master/apiclient> created API client configuration
<master/apiclient> created API client, waiting for the control plane to become ready
<master/apiclient> all control plane components are healthy after 91.042836 seconds
<master/apiclient> waiting for at least one node to register and become ready
<master/apiclient> first node is ready after 3.002105 seconds
<master/apiclient> temporarily unable to update master node metadata due to conflict (will retry)
<master/discovery> created essential addon: kube-discovery, waiting for it to become ready
<master/discovery> kube-discovery is ready after 32.501811 seconds
<master/addons> created essential addon: kube-proxy
<master/addons> created essential addon: kube-dns

Kubernetes master initialised successfully!

You can now join any number of machines by running the following on each node:

kubeadm join --token d38a9c.cd3ce1cd7f932db5 192.168.122.176