如何解決kubeadm init時由于訪問不到國外的鏡像地址報錯

本篇文章為大家展示了如何解決kubeadm init時由于訪問不到國外的鏡像地址報錯，內容簡明扼要并且容易理解，絕對能使你眼前一亮，通過這篇文章的詳細介紹希望你能有所收獲。

kubeadm config images pull 時報錯：
1·W1114 13:07:39.744320   16239 version.go:101] could not fetch a Kubernetes version from the internet: unable to get URL "https://dl.k8s.io/release/stable-1.txt": Get https://dl.k8s.io/release/stable-1.txt: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
W1114 13:07:39.744396   16239 version.go:102] falling back to the local client version: v1.16.2
failed to pull image "k8s.gcr.io/kube-apiserver:v1.16.2": output: Error response from daemon: Get https://k8s.gcr.io/v2/: proxyconnect tcp: dial tcp 172.96.236.117:10070: connect: connection refused
, error: exit status 1
To see the stack trace of this error execute with --v=5 or higher

解決辦法：kubeadm init --image-repository registry.aliyuncs.com/google_containers --ignore-preflight-errors=Swap

如果你的/usr/lib/systemd/system/docker.service文件有類似如下兩行配置
1·Environment="HTTPS_PROXY=http://www.ik8s.io:10080"
2·Environment="NO_PROXY=127.0.0.0/8,172.20.0.0/16"
請把這兩行注釋

上述內容就是如何解決kubeadm init時由于訪問不到國外的鏡像地址報錯，你們學到知識或技能了嗎？如果還想學到更多技能或者豐富自己的知識儲備，歡迎關注億速云行業資訊頻道。