Builds started failing \~1 hour ago. Same issue that was resolved in a thread from 12 days ago. Railpack ignores builder: "DOCKERFILE" from railway.json and auto-detects as a Vite static site instead. * Config: railway.json sets builder: "DOCKERFILE", dockerfilePath: "docker/workers/Dockerfile". Dashboard confirms Dockerfile is configured. * Build log: Railpack v0.22.1 runs instead, detects bun + vite, then fails with secret GCP\_PROJECT\_ID not found (from scanning source code env var references). * Last working deploy: \~9 hours ago, same config, no code/config changes. * Affects 6 services in the same project. One service deployed successfully before the regression rolled out.

Title: Railpack v0.22.x ignoring railway.json Dockerfile configuration (regression)

simply-asking

PROOP

2 months ago

Builds started failing ~1 hour ago. Same issue that was resolved in a thread from 12 days ago.

Railpack ignores builder: "DOCKERFILE" from railway.json and auto-detects as a Vite static site instead.

Config: railway.json sets builder: "DOCKERFILE", dockerfilePath: "docker/workers/Dockerfile". Dashboard confirms Dockerfile is configured.
Build log: Railpack v0.22.1 runs instead, detects bun + vite, then fails with secret GCP_PROJECT_ID not found (from scanning source code env var references).
Last working deploy: ~9 hours ago, same config, no code/config changes.
Affects 6 services in the same project. One service deployed successfully before the regression rolled out.

Solved

4 Replies

Status changed to Awaiting Railway Response Railway • about 2 months ago

brody

EMPLOYEE

2 months ago

Can you please link to a specific deployment where this is the case?

Status changed to Awaiting User Response Railway • about 2 months ago

brody

Can you please link to a specific deployment where this is the case?

simply-asking

PROOP

2 months ago

https://railway.com/project/f979f6e5-bca7-488a-90fb-b25c5813dcb7/service/e092a4e1-05b4-479b-8752-28dda790f220?environmentId=7492483f-3390-4899-b9f0-2b6f9152921c

Status changed to Awaiting Railway Response Railway • about 2 months ago

brody

EMPLOYEE

2 months ago

Can you please try setting the Dockerfile path with a leading forward slash?

Status changed to Awaiting User Response Railway • about 2 months ago

brody

Can you please try setting the Dockerfile path with a leading forward slash?

simply-asking

PROOP

2 months ago

The leading slash didn't fix it either, same behavior, still deployed as a Vite static site.

What did work though, is I copied the Dockerfile to the repo root and pointed dockerfilePath to "Dockerfile". Builds are using the Docker builder correctly now thankfully.

It seems like the issue is Railpack v0.22.x ignoring the builder: "DOCKERFILE" config when the Dockerfile isn't in the repo root. The logs showed "acceptChildOfRepoRoot:false" which skips any subdirectory Dockerfiles regardless of what's in railway.json. This worked fine before the Railpack update... but I think that's whats going on.

Status changed to Awaiting Railway Response Railway • about 2 months ago

Status changed to Solved brody • about 2 months ago

Welcome!