Docker for mac no basic auth credentials

(Note: ECS and ECR are distinct services and have separate policies associated with them). And, I don't know if it's needed for the issue at hand, but while I was at it, I also ended up attaching ECS policies. Rather, they are variously referred to as 'EC2ContainerRegistry' so use 'registry' or some such to filter when looking for the policies, not 'ECR'. Note also that the ECR policies do not have 'ECR' in their names. If there is an IAM user or group with an ID that matches the ID portion of the repository ARN, then this seems likely to be the case. If the https endpoint at the end of a get-login result does not start with the same ID as your repo arn, then you are not going to be able to push.Дepending on how you are using IAM, it may also be necessary set your ECR IAM policies for the appropriate user or group. (Note that it is docker doing the pushing, not aws cli). If this is not the case and you successfully get a docker login string for the wrong user, you will get this error when Docker uses the wrong credentials to try to push the repository to an endpoint associated with a different ID.

You will want to be sure the ID part of the ARN for the repository matches the ID of the profile of the user you are using to issue a get-login. It turns out this problem can rear itself due to authentication mismatches in various places in your AWS account and your aws cli configs.

Tried to push a docker images built locally to the repository but it failed.

Logged in using aws ecr get-login -no-include-email -region ap-northeast-1.

Created a repository on ECR web console.

ID: SR2O:ICK2:6GBS:LBCT:FMEP:BZPA:Z7OG:6XAP:DMHZ:55KX:FHDN:UJHF Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslogД¬ontainerd version: 6e23458c129b551d5c9871e5174f6b1b7f6d1170 Network: bridge host macvlan null overlay

Docker for mac no basic auth credentials