Skip to content
Production Deployment Fails at BUILD_IMAGE
diablostudio12
OP

a month ago

Hi Railway Support,

My production service "Primordial Streaming Web" is failing during the "BUILD_IMAGE" stage.

  • Repository: "Diablostudio12/primehindi-"
  • Branch: "main"
  • Commit: "467b058e0d5aa94e2fc76ca539e70a2dc0cab1c3"
  • Root directory: "frontend"
  • Builder: Railpack
  • Start command: "npm start"

Two deployment attempts failed with "Failed to build an image". The build logs contain only the builder startup banner and no actionable error output. The previous deployment from commit "00b99480" succeeded.

Please investigate the builder-side logs and identify the root cause. Please do not modify or reset the production database.

Thank you.

Solved

1 Reply

Railway
BOT

a month ago

We checked the latest failed deployment. The code upload took about three minutes to finish, and the build failed with the generic "Failed to build an image" message within about two seconds of that upload completing. That was before Railpack planned or ran any build steps, so npm install never started. The build log has only the builder startup line, with no dependency or security-scan error, and none of your service's build settings point to a cause. Based on what we can see, we have not found the root cause.

Because the failure happens before your build steps run, the most useful thing to check is what changed in the repository between the last commit that built successfully and the one that is failing, especially any very large or newly added files or folders under frontend. A change like that would also explain why the upload took so long.

We have not changed anything in your project, and that includes your production database.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

22 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 22 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...