Why is my App Platform build or deployment failing with an out of memory error?

Validated on 24 Jun 2024 • Last edited on 2 Jul 2024

Build Failing with Out of Memory Error

App Platform builds have a combined 8 GB of RAM and disk available, regardless of the plan size. You cannot increase the amount of memory available, so if your build is failing because it runs out of memory, try optimizing your build.

  • Having a large repository and a lot of small files can increase memory overhead, so try decreasing the amount of files in the application to free up more memory during the build. We especially recommend this for static sites.

  • As an alternative, you can build your app as a Docker image and then upload it to DigitalOcean Container Registry. Because this method uses a local build, App Platform skips the build process and deploys directly from the image.

Deployment Failing with Out of Memory Error

The amount of memory available to your app’s deployment depends on the App Platform plan.

If your deployment is running out of memory, you can scale the app to a larger plan.

Why am I receiving 520 status codes from my app?

Your app may have crashed while trying to receive an upload or return a response larger than it has been configured to manage.

Why am I receiving a forbidden error when making changes to my App Platform app?

Your team balance may be past due. Pay your balance to lift restrictions on actions you can take on the platform.

Why does my app not restart when it fails a health check?

If an app’s health check fails, the app currently does not restart. This is because App Platform does not currently support liveness probes. An app only automatically restarts if the app crashes or if its disk or RAM usage exceeds the its limits.

We can't find any results for your search.

Try using different keywords or simplifying your search terms.