I’d like to run the ECR login command and extract the username/password. Then I could use the normal private docker image settings on the docker: section. Is there a way to do something like that? I.d like to do this: docker: - image: acme-private/private-image:321 auth: username: aws…

@aidanrussell The fact that you got that workaround to work is… incredible. Props. We’ve launched official support for authenticating to ECR now: https://circleci.com/blog/aws-ecr-auth-support/

I have a similar issue: [image] Using Private image from ECR Build Environment Hi, How do I pull a private image from ECR ? Am using below config. version: 2 jobs: unit_test: docker: - image: ${ECR}/foo:latest - auth: username: xx …

See my answer to the other thread: [image] Using Private image from ECR Build Environment The aws ecr credential may help here. It deals with providing docker with proper credentials when pulling from ECR. https://github.com/awslabs/amazon-ecr-credential-helper . Regards,…

Support for ECR in CircleCI 2.0 is on the roadmap. @fvanderwerf Do you have a working example of that with a config.yml?

I would like to do this too. It seems a very basic functionality. Can someone post a working config.yml for this please? Presumably it includes a shell script to make the ecr-credential-helper work but guidance much appreciated.

Hello, I got this working with the following config.yml. It’s perhaps a bit messy so let me know if there’s a better way, but it works because the appropriate password is returned as the sixth argument returned by the aws-credential-helper (i.e. the “f” character), and the username as the fourth (i.…

@aidanrussell This is a genius workaround! Thanks a lot for this :thumbsup:

@FelicianoTech Hooray! Much cleaner :relaxed:

can we still use dynamic values as in AIDANRUSSELL’s solution? I have two ECR repos. A development and a production. So my key/secret will be different depending on which branch I am pushing. How can we make the key/secret dynamic?

Take a look at the docs . I think the best way to do what you want, keeping things “official”, is to use a different job for each environment. Then, you can use a different set of environment variables for your AWS creds.

That seems extremely inefficient and redundant. So we’d have to completely duplicate the job just to use different keys?

Is there a way to do pre: or similar at the docker: stage? for ECR?

Build Environment

fvanderwerf September 1, 2017, 9:08am 3

See my answer to the other thread:

Topic		Replies	Views
Using Private image from ECR Build Environment	13	9029	September 13, 2017
Use ECS repository image as build image in CircleCI Build Environment docker , circle-yml , 2.0	0	1240	August 16, 2017
Pushing to AWS ECR repo using ecr orb 8.1.2 Deployments ecr , docker , aws , circle-yml	0	1407	July 28, 2022
Pulling private ECR images in container runners, getting errors Build Environment	0	58	August 30, 2025
Please help - Cannot login to ECR repository Deployments nodejs , circle-yml	1	2056	July 19, 2022

Is there a way to do pre: or similar at the docker: stage? for ECR?

Related topics