Dockerfile Build Fails (Zero Logs)

jamiedavenport

HOBBYOP

18 days ago

I'm seeing repeated failures when building a Dockerfile from our monorepo.

The root, config and Dockerfile all seem to be correct. However, it's hard to debug this because we're getting no build or deploy logs.


{

  "$schema": "https://railway.com/railway.schema.json",

  "build": {

    "builder": "DOCKERFILE",

    "dockerfilePath": "apps/web/Dockerfile"

  },

  "deploy": {

    "healthcheckPath": "/api/healthz",

    "restartPolicyType": "ON_FAILURE",

    "restartPolicyMaxRetries": 10

  }

}

$10 Bounty

2 Replies

Status changed to Open Railway • 18 days ago

keiranross

PROTop 5% Contributor

16 days ago

Try changing the Dockerfile path to include ./:

"dockerfilePath": "./apps/web/Dockerfile"

richwardle

PRO

16 days ago

zero logs usually means the build is failing BEFORE BuildKit boots — config parse or path resolution, not a step inside the Dockerfile. couple of things worth trying in order:

check your service's Root Directory in Settings. if it's set to apps/web already, then dockerfilePath should just be Dockerfile, not apps/web/Dockerfile — the path-doubling silently fails before producing any build log.
run railway up --detach=false locally with the railway cli — that streams build output live in your terminal, bypasses whatever's swallowing the dashboard logs.
if (1) is fine and (2) still shows silence, try setting RAILWAY_DOCKERFILE_PATH=apps/web/Dockerfile as a service env var. duplicates the railway.json config but at a higher precedence layer, useful as a tiebreaker if railway.json isn't being picked up.

Welcome!