Build Failed
Read the build log to fix a failed deployment, from a missing lockfile or Dockerfile to the wrong build method, a failing build step, or build filters.
When a deployment fails while building, open the deployment in the Deployments tab and read its build log. The error is almost always near the end.
Common Causes
- Missing dependencies or lockfile. Commit your lockfile so the build installs the same versions you use locally.
- Wrong build method. If you expect your
Dockerfileto be used, set the build method to Dockerfile. To build without one, use Buildpacks. See Build Configuration. - Dockerfile not found. Out Plane looks for the
Dockerfileunder the root directory. In a monorepo, set the root directory to the app's folder. - A build step fails. A failing compile, test, or build script stops the build. Fix it so it passes locally first.
Build Filters
If a push did not build at all, check your build filters. Ignore rules win over allow rules. A manual deploy ignores filters, which is a quick way to force a build.
Related
Troubleshooting
Find the fix for a failed build, an app that won't start, a port that is not detected, a custom domain that won't resolve, or a database connection error.
Application Won't Start
Fix an app that builds but crashes, keeps restarting, or never reaches Running, from binding to 0.0.0.0 to the start command and missing variables.