pulling kic base image does not respect --image-repository or --image-mirror-country flags for CN registry mirrors #7447

carvendy · 2020-04-06T02:22:38Z

重现问题所需的命令：

失败的命令的完整输出：

minikube start --registry-mirror=https://registry.docker-cn.com --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers --vm-driver=docker --alsologtostderr -v=8

minikube logs命令的输出：

W0406 10:08:19.436876 13086 exit.go:101] Failed to start docker container. "minikube start" may fix it.: recreate: creating host: create: creating: create kic node: create container: failed args: [run -d -t --privileged --security-opt seccomp=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=2200mb --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 gcr.io/k8s-minikube/kicbase:v0.0.8@sha256:2f3380ebf1bb0c75b0b47160fd4e61b7b8fef0f1f32f9def108d3eada50a7a81] output: Unable to find image 'gcr.io/k8s-minikube/kicbase:v0.0.8@sha256:2f3380ebf1bb0c75b0b47160fd4e61b7b8fef0f1f32f9def108d3eada50a7a81' locally
docker: Error response from daemon: Get https://gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.
: exit status 125

使用的操作系统版本：
ubuntu 18.04

The text was updated successfully, but these errors were encountered:

listenerri · 2020-04-07T06:30:53Z

可能跟我的问题一样，我的解决方案是：
https://listenerri.com/2020/04/07/minikube-%E5%90%AF%E5%8A%A8%E5%A4%B1%E8%B4%A5/

sharifelgamal · 2020-04-08T18:26:32Z

The above workaround of building from source will work for now, we'll work on making kicbase available somewhere.

tstromberg · 2020-04-15T20:33:53Z

We don't maintain the CN registry mirror - and do not know how to contact those who do.

wonderfuer · 2020-04-21T06:57:30Z

我也遇到了，正在想办法解决

wonderfuer · 2020-04-21T06:59:34Z

可能跟我的问题一样，我的解决方案是：
https://listenerri.com/2020/04/07/minikube-%E5%90%AF%E5%8A%A8%E5%A4%B1%E8%B4%A5/

你提供的解决方案很有价值。
但是我遇到的情况和你不大一样，我这里是确实连不上外网，本地docker images看不到kicbase镜像；

同时推断，当driver=docker 时，岂不是所有墙内的用户都无法完成minikube start了？

wonderfuer · 2020-04-21T09:24:42Z

可能跟我的问题一样，我的解决方案是：
https://listenerri.com/2020/04/07/minikube-%E5%90%AF%E5%8A%A8%E5%A4%B1%E8%B4%A5/

你好，你分享的经验很有价值！

结合我这边操作发现：
1：我这直接pull下来的镜像Digest是没问题的【这一点看到你那边pull下来就丢了Digest，感觉比较奇怪】
2：我这边是在docker tag时发现，new image的Digest确实丢了；【也就是说直接pull下载才会加上Digest，tag或其它操作就将Digest丢弃了】

供参考，握手！

wonderfuer · 2020-04-21T10:00:54Z

终于算是搞定这个问题了，成功启动minikube的docker驱动的集群，如图：

这个问题预计kicbase没同步到国内镜像源前，大陆用户都会遇到。下面说一下我的思路和方案：

方案1：根据源码重新编译minikube（连带kicbase），如sharifelgamal所述的方案。【根据源码编译带来更多不确定的问题，且minikube刚接触的都是入门用户，此方案不可靠，不推荐】

方案2：让minikube所在的机器走全局代理翻墙，假装身在国外，直接从gcr.io中pull kicbase镜像。【可行，但是kicbase镜像接近1G，翻墙下载估计会比较慢。】

方案3：想各种办法将kicbase镜像搞到本机（通过墙外机器pull下来然后save&load到本机、在国内的某些源中找到kicbase后pull到本地等），然后按照listenerri所提供的帖子中的方案，将镜像重新tag，然后恢复Digest，让minikube能识别，最后搞定。

这里我采用的是方案3，镜像是从阿里云的镜像仓库找到的（感谢上传镜像的同学！），如图：

其中1个的镜像地址：registry.cn-hangzhou.aliyuncs.com/smartliby/kicbase:v0.0.8

tianxiayu007 · 2020-05-03T02:07:39Z

官方已推镜像,大家可以试试~~~
AliyunContainerService#17

wonderfuer · 2020-05-03T02:13:25Z

官方已推镜像,大家可以试试~~~
AliyunContainerService#17

https://yq.aliyun.com/articles/221687
链接404呢？
@lubocheng

tianxiayu007 · 2020-05-03T02:23:34Z

官方已推镜像,大家可以试试~~~
AliyunContainerService#17

https://yq.aliyun.com/articles/221687
链接404呢？
@lubocheng

链接官方自己删除了...可能过些日子就好了

ukihsoroy · 2020-05-13T00:47:39Z

使用新的1.10.0版本指定--base-image registry.cn-hangzhou.aliyuncs.com/google_containers/kicbase:v0.0.10
可以正常启动了。

spartucus · 2020-05-14T03:22:39Z

使用新的1.10.0版本指定--base-image registry.cn-hangzhou.aliyuncs.com/google_containers/kicbase:v0.0.10
可以正常启动了。

好像还是不行：

oc@ocserver:~$ minikube start --vm-driver docker --base-image registry.cn-hangzhou.aliyuncs.com/google_containers/kicbase:v0.0.10 
😄  minikube v1.10.1 on Ubuntu 18.04
✨  Using the docker driver based on existing profile
👍  Starting control plane node minikube in cluster minikube
🚜  Pulling base image ...
E0514 11:17:54.137973    3798 cache.go:129] Error downloading kic artifacts:  getting remote image: Get https://docker.pkg.github.com/v2/: dial tcp: lookup docker.pkg.github.com on 127.0.0.53:53: read udp 127.0.0.1:50986->127.0.0.53:53: i/o timeout
🤷  docker "minikube" container is missing, will recreate.
E0514 11:17:54.383291    3798 oci.go:79] docker daemon seems to be stuck. Please try restarting your docker. Will try to delete anyways: unknown state "minikube": docker inspect minikube --format={{.State.Status}}: exit status 1
stdout:


stderr:
Template parsing error: template: :1:8: executing "" at <.State.Status>: map has no entry for key "State"
🔥  Creating docker container (CPUs=2, Memory=3900MB) ...
🤦  StartHost failed, but will try again: recreate: creating host: create: creating: create kic node: create container: docker run -d -t --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=3900mb -e container=docker --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 --publish=127.0.0.1::5000 docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10: exit status 125
stdout:

stderr:
Unable to find image 'docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10' locally
docker: Error response from daemon: Get https://docker.pkg.github.com/v2/: dial tcp: lookup docker.pkg.github.com on 127.0.0.53:53: read udp 127.0.0.1:36426->127.0.0.53:53: i/o timeout.
See 'docker run --help'.

🤷  docker "minikube" container is missing, will recreate.
E0514 11:19:45.275536    3798 oci.go:79] docker daemon seems to be stuck. Please try restarting your docker. Will try to delete anyways: unknown state "minikube": docker inspect minikube --format={{.State.Status}}: exit status 1
stdout:


stderr:
Template parsing error: template: :1:8: executing "" at <.State.Status>: map has no entry for key "State"
🔥  Creating docker container (CPUs=2, Memory=3900MB) ...
😿  Failed to start docker container. "minikube start" may fix it: recreate: creating host: create: creating: create kic node: create container: docker run -d -t --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=3900mb -e container=docker --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 --publish=127.0.0.1::5000 docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10: exit status 125
stdout:

stderr:
Unable to find image 'docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10' locally
docker: Error response from daemon: Get https://docker.pkg.github.com/v2/: dial tcp: lookup docker.pkg.github.com on 127.0.0.53:53: read udp 127.0.0.1:60680->127.0.0.53:53: i/o timeout.
See 'docker run --help'.


💣  error provisioning host: Failed to start host: recreate: creating host: create: creating: create kic node: create container: docker run -d -t --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=3900mb -e container=docker --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 --publish=127.0.0.1::5000 docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10: exit status 125
stdout:

stderr:
Unable to find image 'docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10' locally
docker: Error response from daemon: Get https://docker.pkg.github.com/v2/: dial tcp: lookup docker.pkg.github.com on 127.0.0.53:53: read udp 127.0.0.1:60680->127.0.0.53:53: i/o timeout.
See 'docker run --help'.


😿  minikube is exiting due to an error. If the above message is not useful, open an issue:
👉  https://github.com/kubernetes/minikube/issues/new/choose

ukihsoroy · 2020-05-14T03:27:21Z

使用新的1.10.0版本指定--base-image registry.cn-hangzhou.aliyuncs.com/google_containers/kicbase:v0.0.10
可以正常启动了。

好像还是不行：

oc@ocserver:~$ minikube start --vm-driver docker --base-image registry.cn-hangzhou.aliyuncs.com/google_containers/kicbase:v0.0.10 
😄  minikube v1.10.1 on Ubuntu 18.04
✨  Using the docker driver based on existing profile
👍  Starting control plane node minikube in cluster minikube
🚜  Pulling base image ...
E0514 11:17:54.137973    3798 cache.go:129] Error downloading kic artifacts:  getting remote image: Get https://docker.pkg.github.com/v2/: dial tcp: lookup docker.pkg.github.com on 127.0.0.53:53: read udp 127.0.0.1:50986->127.0.0.53:53: i/o timeout
🤷  docker "minikube" container is missing, will recreate.
E0514 11:17:54.383291    3798 oci.go:79] docker daemon seems to be stuck. Please try restarting your docker. Will try to delete anyways: unknown state "minikube": docker inspect minikube --format={{.State.Status}}: exit status 1
stdout:


stderr:
Template parsing error: template: :1:8: executing "" at <.State.Status>: map has no entry for key "State"
🔥  Creating docker container (CPUs=2, Memory=3900MB) ...
🤦  StartHost failed, but will try again: recreate: creating host: create: creating: create kic node: create container: docker run -d -t --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=3900mb -e container=docker --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 --publish=127.0.0.1::5000 docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10: exit status 125
stdout:

stderr:
Unable to find image 'docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10' locally
docker: Error response from daemon: Get https://docker.pkg.github.com/v2/: dial tcp: lookup docker.pkg.github.com on 127.0.0.53:53: read udp 127.0.0.1:36426->127.0.0.53:53: i/o timeout.
See 'docker run --help'.

🤷  docker "minikube" container is missing, will recreate.
E0514 11:19:45.275536    3798 oci.go:79] docker daemon seems to be stuck. Please try restarting your docker. Will try to delete anyways: unknown state "minikube": docker inspect minikube --format={{.State.Status}}: exit status 1
stdout:


stderr:
Template parsing error: template: :1:8: executing "" at <.State.Status>: map has no entry for key "State"
🔥  Creating docker container (CPUs=2, Memory=3900MB) ...
😿  Failed to start docker container. "minikube start" may fix it: recreate: creating host: create: creating: create kic node: create container: docker run -d -t --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=3900mb -e container=docker --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 --publish=127.0.0.1::5000 docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10: exit status 125
stdout:

stderr:
Unable to find image 'docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10' locally
docker: Error response from daemon: Get https://docker.pkg.github.com/v2/: dial tcp: lookup docker.pkg.github.com on 127.0.0.53:53: read udp 127.0.0.1:60680->127.0.0.53:53: i/o timeout.
See 'docker run --help'.


💣  error provisioning host: Failed to start host: recreate: creating host: create: creating: create kic node: create container: docker run -d -t --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=3900mb -e container=docker --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 --publish=127.0.0.1::5000 docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10: exit status 125
stdout:

stderr:
Unable to find image 'docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10' locally
docker: Error response from daemon: Get https://docker.pkg.github.com/v2/: dial tcp: lookup docker.pkg.github.com on 127.0.0.53:53: read udp 127.0.0.1:60680->127.0.0.53:53: i/o timeout.
See 'docker run --help'.


😿  minikube is exiting due to an error. If the above message is not useful, open an issue:
👉  https://github.com/kubernetes/minikube/issues/new/choose

试试这个，我正常启动了
minikube start --registry-mirror=https://registry.docker-cn.com --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers --vm-driver=docker --alsologtostderr -v=8 --base-image registry.cn-hangzhou.aliyuncs.com/google_containers/kicbase:v0.0.10

spartucus · 2020-05-14T05:39:02Z

@sigmaol 这样可以了，多谢~

tianxiayu007 · 2020-05-16T03:15:44Z

@sigmaol 这样可以了，多谢~

不行...😪

spartucus · 2020-05-19T04:07:07Z

@lubocheng 不清楚跟网络有没有关系。我在移动网络下，就会失败。换成联通就好了。

medyagh · 2020-06-17T18:33:57Z

@carvendy @spartucus @lubocheng @sigmaol @lubocheng @CHENZHIKANG

in latest version of minikube (v1.11.0) we added the kicbase image(#7943) to docker hub, do you mind trying the latest version and see if that works for you without adding any tricks?

this should just work
download latest minikube verison: https://minikube.sigs.k8s.io/docs/start/

minikube delete
minikube start --driver=docker

here is the image on docker hub:
https://hub.docker.com/r/kicbase/stable

--- google translate:

在最新版本的minikube（v1.11.0）中，我们将kicbase映像添加到了docker hub，您是否介意尝试最新版本并查看它是否对您有效而未添加任何技巧？

这应该工作
下载最新的minikube版本：https://minikube.sigs.k8s.io/docs/start/

minikube删除
minikube start-驱动程序= docker

这是Docker Hub上的图像：
https://hub.docker.com/r/kicbase/stable

medyagh · 2020-06-17T18:37:50Z

this issue is Partially fixed by providing docker hub image but it is still a problem that it should respect the user-provided mirror as said in this comment #7915 (comment)

and minikube should try to download the kicbase image from the user provided mirror for better speed

spartucus · 2020-06-18T03:44:19Z

I tried latest version(v1.11.0) on ubuntu18.04, minikube started and downloaded images successfully! Everything looks good to me, well done!

medyagh · 2020-07-08T18:12:44Z

@spartucus glad to see that was fixed, in v1.11.0 we pushed a fallback image to dockerhub that probably fixed it.
we still need to respect the registrry mirrors for the base image,

so if user specificies a mirror, we should download the base image from that mirror.

danieltanfh95 · 2020-07-12T13:54:35Z

使用新的1.10.0版本指定--base-image registry.cn-hangzhou.aliyuncs.com/google_containers/kicbase:v0.0.10
可以正常启动了。

好像还是不行：

oc@ocserver:~$ minikube start --vm-driver docker --base-image registry.cn-hangzhou.aliyuncs.com/google_containers/kicbase:v0.0.10 
😄  minikube v1.10.1 on Ubuntu 18.04
✨  Using the docker driver based on existing profile
👍  Starting control plane node minikube in cluster minikube
🚜  Pulling base image ...
E0514 11:17:54.137973    3798 cache.go:129] Error downloading kic artifacts:  getting remote image: Get https://docker.pkg.github.com/v2/: dial tcp: lookup docker.pkg.github.com on 127.0.0.53:53: read udp 127.0.0.1:50986->127.0.0.53:53: i/o timeout
🤷  docker "minikube" container is missing, will recreate.
E0514 11:17:54.383291    3798 oci.go:79] docker daemon seems to be stuck. Please try restarting your docker. Will try to delete anyways: unknown state "minikube": docker inspect minikube --format={{.State.Status}}: exit status 1
stdout:


stderr:
Template parsing error: template: :1:8: executing "" at <.State.Status>: map has no entry for key "State"
🔥  Creating docker container (CPUs=2, Memory=3900MB) ...
🤦  StartHost failed, but will try again: recreate: creating host: create: creating: create kic node: create container: docker run -d -t --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=3900mb -e container=docker --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 --publish=127.0.0.1::5000 docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10: exit status 125
stdout:

stderr:
Unable to find image 'docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10' locally
docker: Error response from daemon: Get https://docker.pkg.github.com/v2/: dial tcp: lookup docker.pkg.github.com on 127.0.0.53:53: read udp 127.0.0.1:36426->127.0.0.53:53: i/o timeout.
See 'docker run --help'.

🤷  docker "minikube" container is missing, will recreate.
E0514 11:19:45.275536    3798 oci.go:79] docker daemon seems to be stuck. Please try restarting your docker. Will try to delete anyways: unknown state "minikube": docker inspect minikube --format={{.State.Status}}: exit status 1
stdout:


stderr:
Template parsing error: template: :1:8: executing "" at <.State.Status>: map has no entry for key "State"
🔥  Creating docker container (CPUs=2, Memory=3900MB) ...
😿  Failed to start docker container. "minikube start" may fix it: recreate: creating host: create: creating: create kic node: create container: docker run -d -t --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=3900mb -e container=docker --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 --publish=127.0.0.1::5000 docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10: exit status 125
stdout:

stderr:
Unable to find image 'docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10' locally
docker: Error response from daemon: Get https://docker.pkg.github.com/v2/: dial tcp: lookup docker.pkg.github.com on 127.0.0.53:53: read udp 127.0.0.1:60680->127.0.0.53:53: i/o timeout.
See 'docker run --help'.


💣  error provisioning host: Failed to start host: recreate: creating host: create: creating: create kic node: create container: docker run -d -t --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=3900mb -e container=docker --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 --publish=127.0.0.1::5000 docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10: exit status 125
stdout:

stderr:
Unable to find image 'docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.10' locally
docker: Error response from daemon: Get https://docker.pkg.github.com/v2/: dial tcp: lookup docker.pkg.github.com on 127.0.0.53:53: read udp 127.0.0.1:60680->127.0.0.53:53: i/o timeout.
See 'docker run --help'.


😿  minikube is exiting due to an error. If the above message is not useful, open an issue:
👉  https://github.com/kubernetes/minikube/issues/new/choose

试试这个，我正常启动了
minikube start --registry-mirror=https://registry.docker-cn.com --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers --vm-driver=docker --alsologtostderr -v=8 --base-image registry.cn-hangzhou.aliyuncs.com/google_containers/kicbase:v0.0.10

This works!

priyawadhwa · 2020-08-13T18:42:24Z

It looks like this is working with registry mirrors as well! I'm going to go ahead and close this issue; but if anyone is still seeing errors please reopen by including /reopen in your comment.

SavvyShark · 2021-09-24T03:23:02Z

This is still an issue.

$ minikube version
minikube version: v1.23.2
commit: 0a0ad764652082477c00d51d2475284b5d39ceed
$ minikube start --image-mirror-country=cn --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers
* minikube v1.23.2 on Centos 7.9.2009
* Using the docker driver based on existing profile
* Starting control plane node minikube in cluster minikube
* Pulling base image ...
* Restarting existing docker container for "minikube" ...
* Found network options:
  - HTTP_PROXY=http://192.168.9.9:8080/
  - HTTPS_PROXY=https://192.168.9.9:8080/
  - NO_PROXY=localhost,127.0.0.1,10.0.0.0/8,192.168.0.0/12
! This container is having trouble accessing https://k8s.gcr.io
* To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
* Preparing Kubernetes v1.22.2 on Docker 20.10.8 ...
  - env HTTP_PROXY=http://192.168.9.9:8080/
  - env HTTPS_PROXY=https://192.168.9.9:8080/
  - env NO_PROXY=localhost,127.0.0.1,10.0.0.0/8,192.168.0.0/12
* Verifying Kubernetes components...
  - Using image kubernetesui/dashboard:v2.3.1
  - Using image kubernetesui/metrics-scraper:v1.0.7
  - Using image gcr.io/k8s-minikube/storage-provisioner:v5
* Enabled addons: storage-provisioner, default-storageclass, dashboard
* kubectl not found. If you need it, try: 'minikube kubectl -- get pods -A'
* Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

huxulm · 2021-09-28T11:52:28Z

This is still an issue.

$ minikube version
minikube version: v1.23.2
commit: 0a0ad764652082477c00d51d2475284b5d39ceed
$ minikube start --image-mirror-country=cn --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers
* minikube v1.23.2 on Centos 7.9.2009
* Using the docker driver based on existing profile
* Starting control plane node minikube in cluster minikube
* Pulling base image ...
* Restarting existing docker container for "minikube" ...
* Found network options:
  - HTTP_PROXY=http://192.168.9.9:8080/
  - HTTPS_PROXY=https://192.168.9.9:8080/
  - NO_PROXY=localhost,127.0.0.1,10.0.0.0/8,192.168.0.0/12
! This container is having trouble accessing https://k8s.gcr.io
* To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
* Preparing Kubernetes v1.22.2 on Docker 20.10.8 ...
  - env HTTP_PROXY=http://192.168.9.9:8080/
  - env HTTPS_PROXY=https://192.168.9.9:8080/
  - env NO_PROXY=localhost,127.0.0.1,10.0.0.0/8,192.168.0.0/12
* Verifying Kubernetes components...
  - Using image kubernetesui/dashboard:v2.3.1
  - Using image kubernetesui/metrics-scraper:v1.0.7
  - Using image gcr.io/k8s-minikube/storage-provisioner:v5
* Enabled addons: storage-provisioner, default-storageclass, dashboard
* kubectl not found. If you need it, try: 'minikube kubectl -- get pods -A'
* Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

For my situation is, first minikube pull from gcr.io but failed, then it trys to pull from docker.io.
see below:


I0928 19:47:51.046317    4507 cache.go:180] failed to download gcr.io/k8s-minikube/kicbase:v0.0.27@sha256:89b4738ee74ba28684676e176752277f0db46f57d27f0e08c3feec89311e22de, will try fallback image if available: getting remote image: Get "https://gcr.io/v2/": dial tcp 74.125.204.82:443: i/o timeout
I0928 19:47:51.046372    4507 image.go:75] Checking for docker.io/kicbase/stable:v0.0.27@sha256:89b4738ee74ba28684676e176752277f0db46f57d27f0e08c3feec89311e22de in local docker daemon
I0928 19:47:51.296415    4507 cache.go:146] Downloading docker.io/kicbase/stable:v0.0.27@sha256:89b4738ee74ba28684676e176752277f0db46f57d27f0e08c3feec89311e22de to local cache
I0928 19:47:51.296766    4507 image.go:59] Checking for docker.io/kicbase/stable:v0.0.27@sha256:89b4738ee74ba28684676e176752277f0db46f57d27f0e08c3feec89311e22de in local cache directory
I0928 19:47:51.296831    4507 image.go:119] Writing docker.io/kicbase/stable:v0.0.27@sha256:89b4738ee74ba28684676e176752277f0db46f57d27f0e08c3feec89311e22de to local cache
    > index.docker.io/kicbase/sta...: 299.15 MiB / 355.40 MiB  84.17% 679.12 Ki

SavvyShark · 2021-09-29T07:02:46Z

This is still an issue.

$ minikube version
minikube version: v1.23.2
commit: 0a0ad764652082477c00d51d2475284b5d39ceed
$ minikube start --image-mirror-country=cn --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers
* minikube v1.23.2 on Centos 7.9.2009
* Using the docker driver based on existing profile
* Starting control plane node minikube in cluster minikube
* Pulling base image ...
* Restarting existing docker container for "minikube" ...
* Found network options:
  - HTTP_PROXY=http://192.168.9.9:8080/
  - HTTPS_PROXY=https://192.168.9.9:8080/
  - NO_PROXY=localhost,127.0.0.1,10.0.0.0/8,192.168.0.0/12
! This container is having trouble accessing https://k8s.gcr.io
* To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
* Preparing Kubernetes v1.22.2 on Docker 20.10.8 ...
  - env HTTP_PROXY=http://192.168.9.9:8080/
  - env HTTPS_PROXY=https://192.168.9.9:8080/
  - env NO_PROXY=localhost,127.0.0.1,10.0.0.0/8,192.168.0.0/12
* Verifying Kubernetes components...
  - Using image kubernetesui/dashboard:v2.3.1
  - Using image kubernetesui/metrics-scraper:v1.0.7
  - Using image gcr.io/k8s-minikube/storage-provisioner:v5
* Enabled addons: storage-provisioner, default-storageclass, dashboard
* kubectl not found. If you need it, try: 'minikube kubectl -- get pods -A'
* Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

For my situation is, first minikube pull from gcr.io but failed, then it trys to pull from docker.io. see below:


I0928 19:47:51.046317    4507 cache.go:180] failed to download gcr.io/k8s-minikube/kicbase:v0.0.27@sha256:89b4738ee74ba28684676e176752277f0db46f57d27f0e08c3feec89311e22de, will try fallback image if available: getting remote image: Get "https://gcr.io/v2/": dial tcp 74.125.204.82:443: i/o timeout
I0928 19:47:51.046372    4507 image.go:75] Checking for docker.io/kicbase/stable:v0.0.27@sha256:89b4738ee74ba28684676e176752277f0db46f57d27f0e08c3feec89311e22de in local docker daemon
I0928 19:47:51.296415    4507 cache.go:146] Downloading docker.io/kicbase/stable:v0.0.27@sha256:89b4738ee74ba28684676e176752277f0db46f57d27f0e08c3feec89311e22de to local cache
I0928 19:47:51.296766    4507 image.go:59] Checking for docker.io/kicbase/stable:v0.0.27@sha256:89b4738ee74ba28684676e176752277f0db46f57d27f0e08c3feec89311e22de in local cache directory
I0928 19:47:51.296831    4507 image.go:119] Writing docker.io/kicbase/stable:v0.0.27@sha256:89b4738ee74ba28684676e176752277f0db46f57d27f0e08c3feec89311e22de to local cache
    > index.docker.io/kicbase/sta...: 299.15 MiB / 355.40 MiB  84.17% 679.12 Ki

I tried Windows 10 which behind the same enterprise proxy, with or without --image-mirror-country=cn both works.

C:\Users\zhang>minikube start --image-mirror-country=cn --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers
😄  Microsoft Windows 10 Pro 10.0.18362 Build 18362 上的 minikube v1.23.2
✨  自动选择 docker 驱动
✅  正在使用镜像存储库 registry.cn-hangzhou.aliyuncs.com/google_containers
👍  Starting control plane node minikube in cluster minikube
🚜  Pulling base image ...
    > registry.cn-hangzhou.aliyun...: 27.28 MiB / 355.40 MiB  7.68% 26.99 KiB p^C
C:\Users\zhang>minikube delete --all=true
🔥  正在删除 docker 中的“minikube”…
💀  Removed all traces of the "minikube" cluster.
🔥  成功删除所有配置文件

C:\Users\zhang>minikube start
😄  Microsoft Windows 10 Pro 10.0.18362 Build 18362 上的 minikube v1.23.2
✨  自动选择 docker 驱动
👍  Starting control plane node minikube in cluster minikube
🚜  Pulling base image ...
    > index.docker.io/kicbase/sta...: 27.27 MiB / 355.40 MiB  7.67% 417.39 KiB
    > index.docker.io/kicbase/sta...: 0 B [______________________] ?% ? p/s 38s
    > gcr.io/k8s-minikube/kicbase...: 355.40 MiB / 355.40 MiB  100.00% 759.64 K

k8s-triage-robot · 2021-12-28T07:36:18Z

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot · 2022-01-27T07:47:42Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

sharifelgamal · 2022-02-09T19:28:14Z

This should be fixed.

carvendy added the l/zh-CN Issues in or relating to Chinese label Apr 6, 2020

sharifelgamal changed the title ~~exit status 125~~ kicbase image unavailable in CN registry mirrors Apr 8, 2020

sharifelgamal assigned medyagh Apr 8, 2020

sharifelgamal added the co/docker-driver Issues related to kubernetes in container label Apr 8, 2020

sharifelgamal added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Apr 8, 2020

afbjorklund mentioned this issue Apr 15, 2020

show progress bar for downloading kic base image #7012

Closed

tstromberg added the kind/support Categorizes issue or PR as a support question. label Apr 15, 2020

afbjorklund mentioned this issue Apr 18, 2020

Create archive for the kicbase image #7766

Closed

afbjorklund mentioned this issue Apr 26, 2020

kicbase does not respect --image-repository or --image-mirror-country flags #7915

Closed

tianxiayu007 mentioned this issue May 3, 2020

minikube镜像已经下载不下来了... AliyunContainerService/minikube#17

Closed

This was referenced May 7, 2020

minikube start下载镜像时失败 #8029

Closed

翻墙和阿里云镜像代理下载问题 #8044

Closed

medyagh added the triage/needs-information Indicates an issue needs more information in order to work on it. label Jun 17, 2020

medyagh added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Jun 17, 2020

medyagh changed the title ~~kicbase image unavailable in CN registry mirrors~~ kicbase does not respect --image-repository or --image-mirror-country flags for CN registry mirrors Jun 17, 2020

medyagh added kind/bug Categorizes issue or PR as related to a bug. kind/feature Categorizes issue or PR as related to a new feature. and removed kind/support Categorizes issue or PR as a support question. labels Jun 17, 2020

medyagh removed triage/needs-information Indicates an issue needs more information in order to work on it. kind/bug Categorizes issue or PR as related to a bug. labels Jul 8, 2020

medyagh changed the title ~~kicbase does not respect --image-repository or --image-mirror-country flags for CN registry mirrors~~ pulling kic base image does not respect --image-repository or --image-mirror-country flags for CN registry mirrors Jul 8, 2020

priyawadhwa closed this as completed Aug 13, 2020

medyagh reopened this Sep 24, 2021

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 28, 2021

k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 27, 2022

sharifelgamal closed this as completed Feb 9, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

pulling kic base image does not respect --image-repository or --image-mirror-country flags for CN registry mirrors #7447

pulling kic base image does not respect --image-repository or --image-mirror-country flags for CN registry mirrors #7447

carvendy commented Apr 6, 2020

listenerri commented Apr 7, 2020

sharifelgamal commented Apr 8, 2020

tstromberg commented Apr 15, 2020

wonderfuer commented Apr 21, 2020

wonderfuer commented Apr 21, 2020 •

edited

Loading

wonderfuer commented Apr 21, 2020

wonderfuer commented Apr 21, 2020 •

edited

Loading

tianxiayu007 commented May 3, 2020

wonderfuer commented May 3, 2020 •

edited

Loading

tianxiayu007 commented May 3, 2020

ukihsoroy commented May 13, 2020

spartucus commented May 14, 2020

ukihsoroy commented May 14, 2020

spartucus commented May 14, 2020

tianxiayu007 commented May 16, 2020

spartucus commented May 19, 2020

medyagh commented Jun 17, 2020 •

edited

Loading

medyagh commented Jun 17, 2020 •

edited

Loading

spartucus commented Jun 18, 2020

medyagh commented Jul 8, 2020

danieltanfh95 commented Jul 12, 2020

priyawadhwa commented Aug 13, 2020

SavvyShark commented Sep 24, 2021 •

edited

Loading

huxulm commented Sep 28, 2021

SavvyShark commented Sep 29, 2021 •

edited

Loading

k8s-triage-robot commented Dec 28, 2021

k8s-triage-robot commented Jan 27, 2022

sharifelgamal commented Feb 9, 2022

pulling kic base image does not respect --image-repository or --image-mirror-country flags for CN registry mirrors #7447

pulling kic base image does not respect --image-repository or --image-mirror-country flags for CN registry mirrors #7447

Comments

carvendy commented Apr 6, 2020

listenerri commented Apr 7, 2020

sharifelgamal commented Apr 8, 2020

tstromberg commented Apr 15, 2020

wonderfuer commented Apr 21, 2020

wonderfuer commented Apr 21, 2020 • edited Loading

wonderfuer commented Apr 21, 2020

wonderfuer commented Apr 21, 2020 • edited Loading

tianxiayu007 commented May 3, 2020

wonderfuer commented May 3, 2020 • edited Loading

tianxiayu007 commented May 3, 2020

ukihsoroy commented May 13, 2020

spartucus commented May 14, 2020

ukihsoroy commented May 14, 2020

spartucus commented May 14, 2020

tianxiayu007 commented May 16, 2020

spartucus commented May 19, 2020

medyagh commented Jun 17, 2020 • edited Loading

medyagh commented Jun 17, 2020 • edited Loading

spartucus commented Jun 18, 2020

medyagh commented Jul 8, 2020

danieltanfh95 commented Jul 12, 2020

priyawadhwa commented Aug 13, 2020

SavvyShark commented Sep 24, 2021 • edited Loading

huxulm commented Sep 28, 2021

SavvyShark commented Sep 29, 2021 • edited Loading

k8s-triage-robot commented Dec 28, 2021

k8s-triage-robot commented Jan 27, 2022

sharifelgamal commented Feb 9, 2022

wonderfuer commented Apr 21, 2020 •

edited

Loading

wonderfuer commented Apr 21, 2020 •

edited

Loading

wonderfuer commented May 3, 2020 •

edited

Loading

medyagh commented Jun 17, 2020 •

edited

Loading

medyagh commented Jun 17, 2020 •

edited

Loading

SavvyShark commented Sep 24, 2021 •

edited

Loading

SavvyShark commented Sep 29, 2021 •

edited

Loading