Dockerfile builder not being used despite explicit configuration in monorepo
maxvaljan
PROOP

2 months ago

I have a monorepo with multiple services. The apps/auth service is configured to use a Dockerfile, but Railway keeps using Railpack instead, causing build failures.

Configuration:

  • apps/auth/railway.json explicitly sets "builder": "DOCKERFILE" and "dockerfilePath": "apps/auth/Dockerfile"
  • Root directory is set to . (repo root)
  • UI also shows Dockerfile selected as the builder

Issue: Build logs show root_dir= (empty) and Railpack is being used instead of the Dockerfile. The config-as-code file is found but the builder setting is ignored.

Build logs show:

config-as-code path set as '/apps/auth/railway.json'
...
using build driver railpack-v0.18.0

Despite Dockerfile being explicitly configured, Railpack runs and fails because it can't find a start command in the monorepo root.

Timeline:

  • Yesterday evening: Same exact configuration worked fine
  • This morning: Same configuration now fails
  • No changes made to config or code

Expected: Dockerfile build should be usedActual: Railpack is used, ignoring the builder configuration

Solved

3 Replies

Anonymous
PRO

2 months ago

same Q,

i try:

- Dashboard Builder setting: Dockerfile (confirmed, value set in

railway.toml)

- Tested with Metal Build Environment both ON and OFF — same result

- Manual Redeploy from dashboard: works correctly (uses Dockerfile)

- Git push triggered deploy: fails (ignores Dockerfile, uses

Railpack)


brianquach-accredd
PRO

2 months ago

Experiencing the same. Manual redeploy from dashboard also worked for me (thanks for the tip!).


maxvaljan
PROOP

2 months ago

great, worked for me too


Status changed to Solved nico 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...