docker镜像获取

　　由于墙的的问题，谷歌的镜像很难下载下来，如果k8s的节点没有对应的镜像的话，kubeadm init会一直卡着，下面介绍怎么查看k8s的日志，默认k8s的日志位于/var/log/messages。

当我们安装k8s时，我们可以在另外的窗口打印着k8s的日志，当我们看到有类似于Image not found，就是镜像下载不下来了，镜像和k8s的版本密切联系。

我们这里采取阿里云的镜像,也可以在linux上配置阿里云镜像加速器。

下面给出_k8s_的1.6.2的镜像命令和1.7.1的镜像。1.7.1除部分镜像和1.6.2不同外，其他一致。

• k8s 1.6.2镜像命令 

docker pull registry.cn-hangzhou.aliyuncs.com/google-containers/pause-amd64:3.0
docker tag registry.cn-hangzhou.aliyuncs.com/google-containers/pause-amd64:3.0 gcr.io/google_containers/pause-amd64:3.0

docker pull registry.cn-hangzhou.aliyuncs.com/kube_containers/kube-controller-manager-amd64:v1.6.2
docker tag registry.cn-hangzhou.aliyuncs.com/kube_containers/kube-controller-manager-amd64:v1.6.2 gcr.io/google_containers/kube-controller-manager-amd64:v1.6.2

docker pull registry.cn-hangzhou.aliyuncs.com/kube_containers/kube-apiserver-amd64:v1.6.2
docker tag registry.cn-hangzhou.aliyuncs.com/kube_containers/kube-apiserver-amd64:v1.6.2 gcr.io/google_containers/kube-apiserver-amd64:v1.6.2

docker pull registry.cn-hangzhou.aliyuncs.com/kube_containers/kube-scheduler-amd64:v1.6.2
docker tag registry.cn-hangzhou.aliyuncs.com/kube_containers/kube-scheduler-amd64:v1.6.2 gcr.io/google_containers/kube-scheduler-amd64:v1.6.2

docker pull registry.cn-hangzhou.aliyuncs.com/kube_containers/kube-proxy-amd64:v1.6.2
docker tag registry.cn-hangzhou.aliyuncs.com/kube_containers/kube-proxy-amd64:v1.6.2 gcr.io/google_containers/kube-proxy-amd64:v1.6.2

docker pull registry.cn-hangzhou.aliyuncs.com/google_images/flannel:v0.7.1-amd64
docker tag registry.cn-hangzhou.aliyuncs.com/google_images/flannel:v0.7.1-amd64 quay.io/coreos/flannel:v0.8.0-amd64

docker pull registry.cn-hangzhou.aliyuncs.com/google-containers/etcd-amd64:3.0.17
docker tag registry.cn-hangzhou.aliyuncs.com/google-containers/etcd-amd64:3.0.17 gcr.io/google_containers/etcd-amd64:3.0.17

docker pull registry.cn-hangzhou.aliyuncs.com/google-containers/k8s-dns-sidecar-amd64:1.14.1
docker tag registry.cn-hangzhou.aliyuncs.com/google-containers/k8s-dns-sidecar-amd64:1.14.1 gcr.io/google_containers/k8s-dns-sidecar-amd64:1.14.1

docker pull registry.cn-hangzhou.aliyuncs.com/google-containers/k8s-dns-kube-dns-amd64:1.14.1
docker tag registry.cn-hangzhou.aliyuncs.com/google-containers/k8s-dns-kube-dns-amd64:1.14.1 gcr.io/google_containers/k8s-dns-kube-dns-amd64:1.14.1

docker pull registry.cn-hangzhou.aliyuncs.com/google-containers/k8s-dns-dnsmasq-nanny-amd64:1.14.1
docker tag registry.cn-hangzhou.aliyuncs.com/google-containers/k8s-dns-dnsmasq-nanny-amd64:1.14.1 gcr.io/google_containers/k8s-dns-dnsmasq-nanny-amd64:1.14.1

docker pull registry.cn-hangzhou.aliyuncs.com/google-containers/kubernetes-dashboard-amd64:v1.6.0
docker tag registry.cn-hangzhou.aliyuncs.com/google-containers/kubernetes-dashboard-amd64:v1.6.0 gcr.io/google_containers/kubernetes-dashboard-amd64:v1.6.2

docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/busybox

• k8s 1.7.1不同的镜像

kube-controller-manager-amd64
kube-apiserver-amd64
kube-scheduler-amd64
kube-proxy-amd64

• 1.7.1版本根路径

registry.cn-hangzhou.aliyuncs.com/collapsar/kube-controller-manager-amd64:1.7.1

• 1.7.2版本根路径

registry.cn-hangzhou.aliyuncs.com/szss_k8s/kube-controller-manager-amd64:1.7.2

　　只需要把后面的组件名字和版本文字替换即可替换