如何将容器推送到Google Container Registry(无法创建存储库) [英] How to push container to Google Container Registry (unable to create repository)

查看:360
本文介绍了如何将容器推送到Google Container Registry(无法创建存储库)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

编辑:我只是指责这个平台的不一致。现在,我已经放弃了推送到Google Cloud Container Registry,并创建了一个Ubuntu VM,而我正在做它。我已经投票关闭这个问题,原因如上所述,并且也可能是首先在服务器故障中提出的。感谢大家的帮助!



运行 $ gcloud docker push gcr.io/kubernetes-test-1367/myapp results in:

 推送是指存储库[gcr.io/kubernetes-test-1367/myapp] 
595e622f9b8f :准备
219bf89d98c1:准备
53cad0e0f952:准备
765e7b2efe23:准备
5f2f91b41de9:准备
ec0200a19d76:准备
338cb8e0e9ed:准备
d1c800db26c7:准备
42755cf4ee95:准备
ec0200a19d76:等待
338cb8e0e9ed:等待
d1c800db26c7:等待
42755cf4ee95:等待
被拒绝:无法创建存储库,请检查你有权利这样做。

$ gcloud init 结果: p>

 欢迎!此命令将引导您完成gcloud的配置。 

从当前配置设置[默认]为:
[core]
account =< my_email> @ gmail.com
disable_usage_reporting = True
project = kubernetes-test-1367
您的主动配置是:[default]

注意:这是 Kubernetes:无法创建存储库的重复,但我尝试了他的解决方案它没有帮助我。我尝试追加:v1 / v1 ,并使用 us.gcr.io



编辑:附加信息

  $ gcloud --version 
Google Cloud SDK 116.0.0

bq 2.0.24
bq-win 2.0.18
核心2016.06.24
核心-win 2016.02.05
gcloud
gsutil 4.19
gsutil-win 4.16
kubectl
kubectl-windows-x86_64 1.2.4
windows-ssh-tools 2016.05.13

+

  $ gcloud组件更新

所有组件都是最新的。

+

  $ docker -v 
Docker版本1.12.0-rc3,build 91e29e8,实验


解决方案

我仍然无法从本地机器推送码头图像,但是通过我的帐户授权一个计算实例,并从中推送一个图像。如果遇到此问题,我建议您创建一个Compute Engine实例(为您自己),授权使用可以推送容器并从那里推送的 gcloud auth 的帐户。我有一个Git存储库中的源代码,我可以从中获取代码。


EDIT: I'm just going to blame this on platform inconsistencies. I have given up on pushing to the Google Cloud Container Registry for now, and have created an Ubuntu VM where I'm doing it instead. I have voted to close this question as well, for the reasons stated previously, and also as this should probably have been asked on Server Fault in the first place. Thanks for everyone's help!

running $ gcloud docker push gcr.io/kubernetes-test-1367/myapp results in:

The push refers to a repository [gcr.io/kubernetes-test-1367/myapp]
595e622f9b8f: Preparing
219bf89d98c1: Preparing
53cad0e0f952: Preparing
765e7b2efe23: Preparing
5f2f91b41de9: Preparing
ec0200a19d76: Preparing
338cb8e0e9ed: Preparing
d1c800db26c7: Preparing
42755cf4ee95: Preparing
ec0200a19d76: Waiting
338cb8e0e9ed: Waiting
d1c800db26c7: Waiting
42755cf4ee95: Waiting
denied: Unable to create the repository, please check that you have access to do so.

$ gcloud init results in:

Welcome! This command will take you through the configuration of gcloud.

Settings from your current configuration [default] are:
[core]
account = <my_email>@gmail.com
disable_usage_reporting = True
project = kubernetes-test-1367
Your active configuration is: [default]

Note: this is a duplicate of Kubernetes: Unable to create repository, but I tried his solution and it did not help me. I've tried appending :v1, /v1, and using us.gcr.io

Edit: Additional Info

$ gcloud --version
Google Cloud SDK 116.0.0

bq 2.0.24
bq-win 2.0.18
core 2016.06.24
core-win 2016.02.05
gcloud
gsutil 4.19
gsutil-win 4.16
kubectl
kubectl-windows-x86_64 1.2.4
windows-ssh-tools 2016.05.13

+

$ gcloud components update

All components are up to date.

+

$ docker -v
Docker version 1.12.0-rc3, build 91e29e8, experimental

解决方案

I am still not able to push a docker image from my local machine, but authorizing a compute instance with my account and pushing an image from there works. If you run into this issue, I recommend creating a Compute Engine instance (for yourself), authorizing an account with gcloud auth that can push containers, and pushing from there. I have my source code in a Git repository that I can just pull from to get the code.

这篇关于如何将容器推送到Google Container Registry(无法创建存储库)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆