AWS ECR
Last updated
Was this helpful?
Earthly 0.8
Last updated
Was this helpful?
The AWS Elastic Container Registry (ECR) is a hosted docker repository that requires extra configuration for day-to-day use. This configuration is not typical of other repositories, and there are some considerations to account for when using it with Earthly. This guide will walk you through creating an Earthfile, building an image, and pushing it to ECR.
This guide assumes you have already installed the , and .
No special considerations are needed in the Earthfile itself. You can use SAVE IMAGE just like any other repository.
ECR does not issue permanent credentials. Instead, it relies on your AWS credentials to issue docker credentials. You can follow , but the process will need to be repeated every 12 hours. In practice, this often means lots of glue code in your CI pipeline to keep credentials up to date.
. It may be that you already have the credential helper installed, since it has been included with Docker Desktop as of version . If not, you can follow installation instructions on their GitHub repository here. Here is a sample .docker/config.json to enable the usage of this helper:
Ensure that you have correct permissions to push the images. The ECR helper is aware of the AWS_PROFILE variable; and can work under an assumed role. Here is a minimum set of privileges needed to push to ECR from Earthly:
With the helper installed, no special commands or flags are required. To build and push an image, simply execute the build target with the --push flag.
Using this credential helper; you can also pull images without any special handling in an Earthfile:
And here is how you would run it:
Additional for policy configuration.
If you get a message saying basic credentials not found; your distribution may not have the most recent version installed. A simple workaround is to simply prepend AWS_SDK_LOAD_CONFIG=true to your Earthly invocation. This will force the helper to use the SDK over built-in config when executing. You can track this .
Double-check your AWS credentials, to ensure you have the correct ones set up. aws configure can help you do this. Also, check IAM to ensure you have the correct permissions (see the section above). Finally, if you use IAM assumed roles, ensure that you have assumed the correct role in your terminal session.
If these are in order, the same fix from may help.
If you are using a , the ECR credential helper may cause 401 failures when fetching metadata from the mirrored registry. You can solve this by manually logging in, instead of using the credential helper. Here is an example of logging in manually: