missing backend directory from some snapshots causing build failures
soulmender
HOBBYOP

2 months ago

Project ID: 840f29b4-b407-448b-8d78-ffbfa2547f1b

Environment: production

Service: WorldBuilder

Failed deployment IDs: 2fb68098-af94-4e55-ab1b-1918512f5aca, d142c3fe-558f-4a23-bb20-4fa729b6cc8b, f77c1dee-865c-48e1-8fe0-4778df94f7d4

Working deployment ID: 206f39f2-eebf-4f70-8b57-666f67d57964

Issue: Snapshot system serving incomplete code archives intermittently since hardware incident — backend/ directory missing from some snapshots

Solved$10 Bounty

14 Replies

soulmender
HOBBYOP

2 months ago

Don't know if issues are related, but auto deply has also stopped working


2 months ago

Is this a Docker-built service?


soulmender
HOBBYOP

2 months ago

Yes — the service uses a Dockerfile at backend/Dockerfile with the build context set to the repo root. The Dockerfile copies from backend/ subdirectories (e.g., COPY backend/app/ app/). This worked for every deployment until the March 17 EU West hardware incident. The working deployment (206f39f2) used the exact same Dockerfile successfully.


2 months ago

At which step is the build failing?

When trying to find the Dockerfile, or during the actual Dockerfile steps?


2 months ago

Could you possibly also show the build logs? the error?


soulmender
HOBBYOP

2 months ago

No Dockerfile steps (FROM, COPY, RUN, etc.) are reached. The file exists in the repo at backend/Dockerfile and hasn't changed — the working deployment (206f39f2) used the exact same file.

The auto-deploy from GitHub pushes also stopped triggering. Disconnecting and reconnecting the repo didn't fix it. Manual redeploys from the dashboard (even of the previously-successful deployment) now also fail with the same missing Dockerfile error.

Here are the logs anyway:

2026-03-18T16:59:51.692789764Z [inf] scheduling build on Metal builder "builder-rnsvgb"

2026-03-18T16:59:54.022920132Z [inf] fetched snapshot sha256:122e270613f094f27f227f142b84c2726a5f50f9b0eb1fbc5181f9710b3315fc (33 MB bytes)

2026-03-18T16:59:54.023022836Z [inf] fetching snapshot

2026-03-18T16:59:55.094756120Z [inf] unpacking archive

2026-03-18T16:59:56.082363595Z [err] couldn't locate the dockerfile at path backend/Dockerfile in code archive

2026-03-18T16:59:56.082376344Z [err] - not found at backend/Dockerfile

2026-03-18T16:59:56.082377666Z [err] - not found at backend/Dockerfile


2 months ago

What happens if you try to reselect the Dockerfile in service settings?


soulmender
HOBBYOP

2 months ago

The Dockerfile path is set in railway.toml (checked into the repo), not in the UI settings — so I can't reselect it from the dashboard. The value is backend/Dockerfile and hasn't changed. The same railway.toml worked fine for the previous successful deployment. It hasn't been touched in a long time


2 months ago

I understand that you may not have done anything to have caused this, but right now we're trying to get your deployments to not fail

Is the value /backend/Dockerfile or backend/Dockerfile?


soulmender
HOBBYOP

2 months ago

[build]

builder = "DOCKERFILE"

dockerfilePath = "backend/Dockerfile"

watchPatterns = ["backend/**", "railway.toml"]


2 months ago

could you prefix a / to both the dockerfilepath and watchpatterns?


soulmender
HOBBYOP

2 months ago

It build, now. though the issue with not picking up automatic deployment on changes to main are still failing. Thanks fo now, I'll see if this sticks


2 months ago

If you added it to watchpaths it shouldddd work


soulmender
HOBBYOP

2 months ago

Yeah, I did. Thanks


Status changed to Solved passos about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...