Adding caching options to amplify.yml causes "Build container ran out of memory" #3925
Open
3 tasks done
Labels
feature-request
New feature or request
Before opening, please confirm:
Amplify Hosting feature
Deployments
Is your feature request related to a problem? Please describe:
When I add the following to my
amplify.yaml
, my builds begin to fail with the error message:Build container ran out of memory
I can confirm that the build logs show our code builds successfully, all the way to the end of our build steps...and the failure happens after our frontend is already built and ready to be deployed.
Removing the cache settings returns our build pipelines to a working condition.
We're using pnpm version 9 with workspaces and the following .npmrc settings:
Based on information I've found in other issues, I even do the following in our pipeline, in an attempt to side-step memory-related limitations for my builds:
Describe how you'd like this feature to work
We'd like to benefit from using the cache for faster builds.
The text was updated successfully, but these errors were encountered: