这期内容当中小编将会给大家带来有关docker及kubernetes国内源和镜像源的解决方式是什么，文章内容丰富且以专业的角度为大家分析和叙述，阅读完这篇文章希望大家可以有所收获。
最近在使用kubeadm时，被各种连接不上搞到崩溃。费了很多力气，基本都解决了。这里统一整理了国内的一些镜像源，apt源，kubeadm源等，以便查阅。
国内镜像源
Azure China提供了目前用过的质量最好的镜像源。无论是速度还是覆盖范围。而且都支持匿名拉取，也就是不需要登录。这点特别友好。
这里，我开发了一个小的脚本azk8spull，这个脚本可以自动根据镜像名称进行解析，转换为azure的mirror镜像源域名。并进行拉取。拉取完成后会自动进行tag重命名为原本的镜像名。该脚本已经开源在 https://github.com/xuxinkun/littleTools#azk8spull 上。以下是样例。
[root@node-64-216 ~]# azk8spull quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.24.1## azk8spull try to pull image from mirror quay.azk8s.cn/kubernetes-ingress-controller/nginx-ingress-controller:0.24.1.0.24.1: Pulling from kubernetes-ingress-controller/nginx-ingress-controllerDigest: sha256:76861d167e4e3db18f2672fd3435396aaa898ddf4d1128375d7c93b91c59f87fStatus: Image is up to date for quay.azk8s.cn/kubernetes-ingress-controller/nginx-ingress-controller:0.24.1## azk8spull try to tag quay.azk8s.cn/kubernetes-ingress-controller/nginx-ingress-controller:0.24.1 to quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.24.1.## azk8spull finish pulling.[root@node-64-216 ~]# azk8spull k8s.gcr.io/pause-amd64:3.1## azk8spull try to pull image from mirror gcr.azk8s.cn/google_containers/pause-amd64:3.1.3.1: Pulling from google_containers/pause-amd64Digest: sha256:59eec8837a4d942cc19a52b8c09ea75121acc38114a2c68b98983ce9356b8610Status: Image is up to date for gcr.azk8s.cn/google_containers/pause-amd64:3.1## azk8spull try to tag gcr.azk8s.cn/google_containers/pause-amd64:3.1 to k8s.gcr.io/pause-amd64:3.1.## azk8spull finish pulling.azk8s.cn支持的镜像转换如下列表。
Note:
k8s.gcr.io would redirect to gcr.io/google-containers, following image urls are identical:
k8s.gcr.io/pause-amd64:3.1gcr.io/google_containers/pause-amd64:3.1debian apt源
debian的apt的国内源更换为163的源，可以显著加速。
mv /etc/apt/sources.list /etc/apt/sources.list.bak# 换下源echo "deb http://mirrors.163.com/debian/ stretch main non-free contribdeb http://mirrors.163.com/debian/ stretch-updates main non-free contribdeb http://mirrors.163.com/debian/ stretch-backports main non-free contribdeb-src http://mirrors.163.com/debian/ stretch main non-free contribdeb-src http://mirrors.163.com/debian/ stretch-updates main non-free contribdeb-src http://mirrors.163.com/debian/ stretch-backports main non-free contribdeb http://mirrors.163.com/debian-security/ stretch/updates main non-free contribdeb-src http://mirrors.163.com/debian-security/ stretch/updates main non-free contrib" > /etc/apt/sources.listkubeadm源
kubeadm直接使用阿里云的源即可。速度也比较快。
# Debian/Ubuntuapt-get update && apt-get install -y apt-transport-httpscurl -s https://mirrors.aliyun.com/kubernetes/apt/doc/apt-key.gpg | apt-key add -cat <<EOF >/etc/apt/sources.list.d/kubernetes.listdeb https://mirrors.aliyun.com/kubernetes/apt/ kubernetes-xenial mainEOFapt-get updateapt-get install -y kubelet kubeadm kubectl# CentOS/RHEL/Fedoracat <<EOF > /etc/yum.repos.d/kubernetes.repo[kubernetes]name=Kubernetesbaseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64/enabled=1gpgcheck=1repo_gpgcheck=1gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpgEOFsetenforce 0yum install -y kubelet kubeadm kubectl上述就是小编为大家分享的docker及kubernetes国内源和镜像源的解决方式是什么了，如果刚好有类似的疑惑，不妨参照上述分析进行理解。如果想知道更多相关知识，欢迎关注编程网行业资讯频道。
