Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failed to pull image registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:v1.8.0: output: Error response from daemon: manifest for registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:v1.8.0 not found: manifest unknown: manifest unknown #12021

Closed
XiangyuZhu opened this issue Jul 20, 2021 · 8 comments
Labels
area/registry registry related issues kind/support Categorizes issue or PR as a support question. l/zh-CN Issues in or relating to Chinese

Comments

@XiangyuZhu
Copy link

重现问题所需的命令

失败的命令的完整输出

minikube logs命令的输出

使用的操作系统版本

@XiangyuZhu XiangyuZhu added the l/zh-CN Issues in or relating to Chinese label Jul 20, 2021
@XiangyuZhu
Copy link
Author

sudo minikube start --vm-driver=none --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers

@ajasonwang
Copy link

Interesting, only missing registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:v1.8.0 but other images are there, can anyone from ali fix it?

@zishiguo
Copy link

I also meet this question

@yangsongx
Copy link

yangsongx commented Jul 28, 2021

Yes, I met the same issue!!!

I think probably this is caused as v1.8.0 of coredns's docker image path has an extra /coredns/ field, while older version of coredns had no such extra field....

A workaround ways is:

  1. You need to get the coredns image somewhere(via VPN in China, or something else)
  2. Using docker tag to mark this coredns to aliyun's, such as:
docker tag k8s.gcr.io/coredns/coredns:v1.8.0 registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:v1.8.0
  1. Then continue your work from then

@spowelljr spowelljr added the kind/support Categorizes issue or PR as a support question. label Jul 30, 2021
@spowelljr
Copy link
Member

Thanks for finding the root of this issue. The problem is the minikube maintainers aren't the one's maintaining the Alibaba registry, our goal is to maintain the Alibaba registry ourselves in the future though. Until then, if one of the people maintaining the registry come across this issue maybe they can help out. Sorry for the inconvenience.

@spowelljr spowelljr added the area/registry registry related issues label Aug 11, 2021
@th110
Copy link

th110 commented Aug 13, 2021

xiong dei,I met the same issue.I have tried, pull coredns from other registry-mirror,and then ,use 'docker tag' modify '1.8.0' to 'v1.8.0',but it doesnot work.Maybe the only way we can do ,is downloading all required images and building local registory

@Bytesu
Copy link

Bytesu commented Aug 22, 2021

docker pull coredns/coredns:1.8.0
docker tag coredns/coredns:1.8.0 registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:v1.8.0
docker rmi coredns/coredns:1.8.0
minikube image load registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:v1.8.0
sudo minikube start --image-repository='registry.cn-hangzhou.aliyuncs.com/google_containers’ --image-mirror-country='cn’

like above . it's works for me.

@sharifelgamal
Copy link
Collaborator

This issue should be fixed with #11785 and is in the current release of minikube, 1.23.2. I'm going to go ahead and close this issue, but if issues remain please comment on this and I'll reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/registry registry related issues kind/support Categorizes issue or PR as a support question. l/zh-CN Issues in or relating to Chinese
Projects
None yet
Development

No branches or pull requests

8 participants