【Docker】Error: No such image: gotok8s/kube-proxy:v1.16.5

1.背景

背景请参考：【Docker】Mac下Docker启动Kubernetes处于一直启动中（卡死

(base) lcc@lcc github$  git clone https://github.com/gotok8s/k8s-docker-desktop-for-mac.git
Cloning into 'k8s-docker-for-mac'...
remote: Enumerating objects: 10, done.
remote: Counting objects: 100% (10/10), done.
remote: Compressing objects: 100% (6/6), done.
remote: Total 223 (delta 2), reused 7 (delta 2), pack-reused 213
Receiving objects: 100% (223/223), 850.63 KiB | 53.00 KiB/s, done.
Resolving deltas: 100% (83/83), done.
(base) lcc@lcc github$ cd k8s-docker-for-mac/
(base) lcc@lcc k8s-docker-for-mac$ sh load_images.sh
images found.
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: TLS handshake timeout
Error response from daemon: No such image: gotok8s/kube-proxy:v1.16.5
Error: No such image: gotok8s/kube-proxy:v1.16.5
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: TLS handshake timeout
Error response from daemon: No such image: gotok8s/kube-controller-manager:v1.16.5
Error: No such image: gotok8s/kube-controller-manager:v1.16.5
Error response from daemon: Get https://registry-1.docker.io/v2/gotok8s/kube-scheduler/manifests/v1.16.5: Get https://auth.docker.io/token?scope=repository%3Agotok8s%2Fkube-scheduler%3Apull&service=registry.docker.io: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Error response from daemon: No such image: gotok8s/kube-scheduler:v1.16.5
Error: No such image: gotok8s/kube-scheduler:v1.16.5
v1.16.5: Pulling from gotok8s/kube-apiserver
39fafc05754f: Downloading  3.754MB
fdffd0d7a0bb: Downloading  1.604MB
error pulling image configuration: Get https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/fc/fc838b21afbb7b68dcfc223ed02a501943c93aee38f73d914eb17639df3f714f/data?verify=1589727214-h6dEJMF9amazzLd%2FTv%2FvTWJmnEs%3D: EOF
Error response from daemon: No such image: gotok8s/kube-apiserver:v1.16.5
Error: No such image: gotok8s/kube-apiserver:v1.16.5
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Error response from daemon: No such image: gotok8s/coredns:1.6.2
Error: No such image: gotok8s/coredns:1.6.2
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: TLS handshake timeout
Error response from daemon: No such image: gotok8s/pause:3.1
Error: No such image: gotok8s/pause:3.1
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: TLS handshake timeout
Error response from daemon: No such image: gotok8s/etcd:3.3.15-0
Error: No such image: gotok8s/etcd:3.3.15-0
(base) lcc@lcc k8s-docker-for-mac$

为什么下载不了呢？我才想一定是配置，想看看这个脚本在干嘛

(base) lcc@lcc k8s-docker-desktop-for-mac$ vi load_images.sh
#!/bin/bash

file="images"

if [ -f "$file" ]
then
  echo "$file found."

  while IFS='=' read -r key value
  do
    #echo "${key}=${value}"
    docker pull ${value}
    docker tag ${value} ${key}
    docker rmi ${value}
  done < "$file"

else
  echo "$file not found."
fi

发现这里没有什么，然后进入

(base) lcc@lcc k8s-docker-desktop-for-mac$ vi  images

k8s.gcr.io/kube-proxy:v1.16.5=kubernetes/kube-proxy:v1.16.5
k8s.gcr.io/kube-controller-manager:v1.16.5=kubernetes/kube-controller-manager:v1.16.5
k8s.gcr.io/kube-scheduler:v1.16.5=kubernetes/kube-scheduler:v1.16.5
k8s.gcr.io/kube-apiserver:v1.16.5=kubernetes/kube-apiserver:v1.16.5
k8s.gcr.io/coredns:1.6.2=kubernetes/coredns:1.6.2
k8s.gcr.io/pause:3.1=kubernetes/pause:3.1
k8s.gcr.io/etcd:3.3.15-0=kubernetes/etcd:3.3.15-0

发现里面一堆感觉像是git地址的东东，打开发现有些已经不存在了，有些在kubernetes项目下，改成如下

k8s.gcr.io/kube-proxy:v1.16.5=kubernetes/kube-proxy:v1.16.5
k8s.gcr.io/kube-controller-manager:v1.16.5=kubernetes/kube-controller-manager:v1.16.5
k8s.gcr.io/kube-scheduler:v1.16.5=kubernetes/kube-scheduler:v1.16.5
k8s.gcr.io/kube-apiserver:v1.16.5=kubernetes/kube-apiserver:v1.16.5
k8s.gcr.io/coredns:1.6.2=kubernetes/coredns:1.6.2
k8s.gcr.io/pause:3.1=kubernetes/pause:3.1
k8s.gcr.io/etcd:3.3.15-0=kubernetes/etcd:3.3.15-0

但是仍然报错，查看发现版本不对,然后修改版本发现乱七八糟的有的有有的没有