Fix and analyze failed deployments with these troubleshooting steps.
Build process failed Unknown build fail typeOpen the Deployment logs and look for errors similar to the following:
===> DETECTING ERROR: No buildpack groups passed detection. ERROR: Please check that you are running against the correct path. ERROR: failed to detect: no buildpacks participating ERROR: failed to build: executing lifecycle: failed with status code: 20These errors occur when there isn’t enough information to correctly detect the type of application. This is usually caused by one of the following:
The build failed because the process exited too early. This probably means the system ran out of memory or someone called kill -9
on the process.
This is usually caused by insufficient system memory in the build machine for the application.
To resolve this error, increase the size of your application’s build machine. Go to Settings > Build > Update resource, choose a larger build machine and click Update resource again to confirm the change.
Please switch to one of our newer ‘heroku/builder:*’ builder images, such as ‘heroku/builder:22’This may be due to an updated build configuration in Sevalla. To resolve this:
heroku-php-apache2 /public
for all other PHP applications, remove the Start command.Build process failed Unknown build fail typeIf the rollout process fails immediately, or if the build process fails, no pods are created, and runtime logs do not exist, an incorrect start command in the web process is most often the cause (or an incorrect
ENTRYPOINT
in the Dockerfile if your application is built from a Dockerfile).
If the rollout process runs for a minute or two and then fails, this usually means the pods were created, but something went wrong, and the process stopped. In this case, you should check the deployment runtime logs to identify any error messages. The error messages can help you identify bugs in the application’s code so you can debug the issue.
If you cannot identify the issue, check the following, and if the issue persists, contact our Support team.
require
key with the PHP version, like the following:
ENTRYPOINT
in the Dockerfile to run a container. For more information about how to specify your application’s ENTRYPOINT
, see the Dockerfile reference.
Environment variables for your application.
\
).\
).ERROR: failed to solve: process “/bin/bash -ol pipefail -c npm run build” did not complete successfully: exit code: 126This error is caused when the
vendor
and node_modules
folders are present within the repository. These folders are generated during the build process and should, therefore, be removed from the repository to resolve this issue.