无法将图像推送到Amazon ECR -由于“没有基本的身份验证凭据”而失败

我正在尝试将docker映像推送到Amazon ECR注册表。我使用docker客户端docker版本1.9.1，构建a34a1d5。我使用aws ecr get-login -region us-east-1来获得docker登录信用。然后我成功登录这些学分如下:

docker login -u AWS -p XXXX -e none https://####.dkr.ecr.us-east-1.amazonaws.com
WARNING: login credentials saved in /Users/ar/.docker/config.json
Login Succeeded

但当我试图推动我的图像，我得到以下错误:

$ docker push ####.dkr.ecr.us-east-1.amazonaws.com/image:latest
The push refers to a repository [####.dkr.ecr.us-east-1.amazonaws.com/image] (len: 1)
bcff5e7e3c7c: Preparing 
Post https://####.dkr.ecr.us-east-1.amazonaws.com/v2/image/blobs/uploads/: no basic auth credentials

我确保aws用户具有正确的权限。我还确保存储库允许用户推送到它。为了确保这不是一个问题，我将注册表设置为允许所有用户完全访问。没有什么可以改变“no basic auth credentials”错误。我不知道如何开始调试，因为所有的流量都是加密的。

更新

So I had a bit of Homer Simpson D'Oh moment when I realized the root cause of my problem. I have access to multiple AWS accounts. Even though I was using aws configure to set my credentials for the account where I had setup my repository the aws cli was actually using the environment variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. So when I did aws ecr get-login it was returning a login for the wrong account. I failed to notice that the account numbers were different until I just went back now to try some of the proposed answers. When I remove the environment variables everything works correctly. I guess the motto of the story is if you hit this error, make sure that the repository you are logging into matches the tag you have applied to the image.

当前回答

Make sure you have created the ECR registry first. Then as per the ECR Push Command Instructions, cut and paste the following commands Execute the docker login command (eval on Mac/Linux skips the cut-and-paste) eval $(aws ecr get-login --region us-east-1) add --profile if you use multiple AWS Accounts eval $(aws ecr get-login --region us-east-1 --profile your-profile) docker build -t image-name . docker tag image-name:latest ############.dkr.ecr.us-east-1.amazonaws.com/image-name:latest docker push ############.dkr.ecr.us-east-1.amazonaws.com/image-name:latest

如果出现错误，请确保再次运行所有命令!使用aws ecr get-login获得的凭据是临时的，将会过期。

2016-10-31 03:57:04

其他回答

如果ecr登录失败，通常会抛出此错误。我使用的是windows系统，我在管理员模式下使用“Powershell”首先登录到ecr。

Invoke-Expression $(aws ecr get-login --no-include-email)

这应该会输出“Login succeeded”。

2019-12-09 02:12:10

这只是为了防止有人像我一样从来没有读过F手册我遵循了上面建议的所有步骤，比如

aws ecr get-login-password --region eu-west-1 | docker login --username AWS --password-stdin 123456789.dkr.ecr.eu-west-1.amazonaws.com

而且总是没有基本的认证证书我创建了一个名为

123456789.dkr.ecr.eu-west-1.amazonaws.com/my.registry.com/namespace

并试图推广一个叫alpine:latest的图片

123456789.dkr.ecr.eu-west-1.amazonaws.com/my.registry.com/namespace/alpine:latest
2c6e8b76de: Preparing
9d4cb0c1e9: Preparing
1ca55f6ab4: Preparing
b6fd41c05e: Waiting
ad44a79b33: Waiting
2ce3c1888d: Waiting
no basic auth credentials

愚蠢的错误在我的代表，因为我必须创建一个注册表在ecr使用完整的容器路径。我使用完整的容器路径创建了一个新的注册中心，而不是在名称空间上结束

123456789.dkr.ecr.eu-west-1.amazonaws.com/my.registry.com/namespace/alpine

又低又快

123456789.dkr.ecr.eu-west-1.amazonaws.com/my.registry.com/namespace/alpine:latest 
The push refers to repository [123456789.dkr.ecr.eu-west-1.amazonaws.com/my.registry.com/namespace/alpine]
0c8667b5b: Pushed
730460948: Pushed
1.0: digest: sha256:e1f814f3818efea45267ebfb4918088a26a18c size: 7

工作很好

2020-09-16 02:51:18

更新

由于AWS CLI版本2 - AWS ecr get-login已弃用，正确的方法是AWS ecr get-login-password。

因此，正确的最新答案如下: docker login -u AWS -p $(AWS ecr get-login-password——region us-east-1) xxxxxxxx.dkr.ecr.us-east-1.amazonaws.com

2020-04-02 07:40:44

如果您使用多个配置文件，并且需要登录到一个不是默认配置文件的配置文件，您需要使用此命令登录:

$(AWS_PROFILE=<YOUR PROFILE> aws ecr get-login --no-include-email --region eu-west-1)

2018-11-14 14:13:56

刚刚进行了更新，从AWS中删除了get-login，而是使用get-login-password:

sudo docker login -u AWS -p $(aws ecr get-login-password --region <region> - 
-profile <profile>) <account id>.dkr.ecr.eu-north-1.amazonaws.com

如果使用默认凭证，不要忘记删除——profile标志

2020-07-23 14:27:42

无法将图像推送到Amazon ECR -由于“没有基本的身份验证凭据”而失败

推荐文章

最新文章

标签