Skip to content
Failing - BUILD_IMAGE stage with the generic error
ben-adewa
OP

11 days ago

We have experienced two consecutive failed deployments on our production service, both failing at the BUILD_IMAGE stage with the generic error: "Failed to build an image."

Both deployments produced completely empty Railpack build logs:

Deployment 410b641e-9843-4753-9f3b-a4dcffa9ee92 (commit 25343a0d)

Deployment cd8c7cbe-cc5a-4ea3-8e59-2a3f210e86ca (commit 016c7ac0)

Both deployments used our GitHub-connected source. The same code builds successfully locally, and our existing production deployment remains healthy on commit 98558540.

We understand there is currently a reported GitHub outage affecting Railway builds. Could you confirm whether our failures are related to this incident and advise when it is safe to retry?

We would appreciate your assistance in confirming that there is no underlying issue with our service or deployment configuration.

Thank you for your help.

Solved

1 Reply

Railway
BOT

11 days ago

We're sorry for the trouble. Both failed deployments line up with the GitHub Outage Affecting Builds incident: the build failed in under a minute while pulling your GitHub source, before any build step ran, which is why the build logs are empty. Your current production deployment is not affected.

The incident is still open and we don't have an ETA from GitHub yet. Deploys started manually or from the CLI with railway up are not affected in the meantime. Follow updates at the incident page.


Status changed to Awaiting User Response Railway • 11 days ago


Railway
BOT

3 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 • 3 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...