没有推送到GCR的权限-但是该项目的所有者 [英] Don't have permission to push to GCR - but am owner of the project

查看:79
本文介绍了没有推送到GCR的权限-但是该项目的所有者的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

推送到 eu.gcr.io/my-project-name/my-image:tag ,我得到:

未经授权:您没有执行此操作所需的权限,并且您的凭据可能无效.要验证您的请求,请按照以下步骤操作:https://cloud.google.com/container-registry/docs/advanced-authentication

我已经安装了gcloud,并且当我使用 gcloud身份验证列表时,我看到所选帐户是项目的所有者.

I have gcloud installed, and when I use gcloud auth list, I see the selected account is the owner of the project.

我已经运行了 gcloud auth configure-docker ,并且我的Docker配置文件包含 gcloud 作为凭据助手.我已经确认docker使用的是相同的配置,因为如果我暂时清空配置, docker push 会给出不同的错误.

I've run gcloud auth configure-docker and my Docker config file contains gcloud as credential helpers, accordingly. I've confirmed that docker is using the same config, because if I temporarily empty out the config, docker push gives a different error.

我还用过:

docker login -u oauth2accesstoken -p'token_here'https://eu.gcr.io .

这是一台新笔记本电脑,用户以前可以很好地推送到注册表...我很迷茫.

This is a new laptop, and the user was fine to push to the registry previously... I'm quite lost.

版本:

Google Cloud SDK 310.0.0
bq 2.0.60
core 2020.09.11
gsutil 4.53


Client: Docker Engine - Community
 Azure integration  0.1.15
 Version:           19.03.12
 API version:       1.40
 Go version:        go1.13.10
 Git commit:        48a66213fe
 Built:             Mon Jun 22 15:43:18 2020
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.12
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.10
  Git commit:       48a66213fe
  Built:            Mon Jun 22 15:49:27 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

推荐答案

我遇到了同样的问题-这是在本周初最新的Docker桌面更新之后发生的.我禁用了启用云体验"在命令行"中桌面设置窗口中的选项.然后它起作用了...

I had the same problem - which happened after the latest Docker Desktop update earlier this week. I disabled "Enable Cloud Experience" in the "Command Line" options in the Desktop Settings window. It then worked ...

这篇关于没有推送到GCR的权限-但是该项目的所有者的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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