I encountered the error
“BUILD_CONTAINER_UNABLE_TO_PULL_IMAGE: Unable to pull customer’s container image. CannotPullContainerError: Error response from daemon: too many requests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading.”
This error caused my web application front end to be stuck at Provisioning.
After conducting extensive research, I found a solution to the issue. The error is related to the inability to pull the container image due to Docker Hub’s pull rate limit. By following the steps mentioned below, I was able to resolve the issue and redeploy my application. The error seems to be a common issue, and other users have also faced similar challenges. Some have suggested using a custom image stored in AWS ECR as a workaround. However, the solution I found worked effectively for me.
To resolve the “BUILD_CONTAINER_UNABLE_TO_PULL_IMAGE” error in AWS Amplify, I followed these steps:
- Click on the name of your app.
- Under “App Settings,” find the sub-menu named “Build Settings.”
- Click on “Build Settings.”
- Under Build Settings, find the “Build Image Setting” section.
- Click on “Edit“
- A new modal box will appear, click on the build image dropdown, and select “Amazon:Linux:2023.”
- Click on “Save” and redeploy your current version.
The steps I followed are in line with the official AWS Amplify documentation, which guides on configuring build settings for an app deployed with Amplify Hosting
I hope this information helps you in resolving the AWS Amplify issue you are facing. If you encounter any further challenges, feel free to reach out for assistance.
