The config file correctly specifies DOCKERFILE, but all deployments run as RAILPACK and fail instantly.
adambornak
FREEOP

2 months ago

Every deployment is failing at the build stage with no log output, and the builder override in railway.json is not being applied. The config file correctly specifies DOCKERFILE, but all deployments run as RAILPACK and fail instantly. Contact Railway support to investigate the broken service configuration.

Solved$10 Bounty

2 Replies

Status changed to Open Railway about 2 months ago


2 months ago

I'm trying to reproduce this, give me one minute


Status changed to Awaiting User Response Railway about 2 months ago


2 months ago

I couldn't repro this, so this tells me this isn't a railway.json issue.

Please check your root path and see if it's the same path your Dockerfile is at. Also note that railway.json does not follow the root directory setting, it must be at the repo root according to the docs.


Status changed to Awaiting Railway Response Railway about 2 months ago


Status changed to Awaiting User Response Railway about 2 months ago


Railway
BOT

a month 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 about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...