RAILWAY_DOCKERFILE_PATH env var no longer detecting my Dockerfile
All of my services (projectid
project/b5af5fab-625a-4f48-8ec7-3aa80dd451ed began falling back to nixpacks today. Was there a regression with RAILWAY_DOCKERFILE_PATH?
This is affecting some time-sensitive prod deployments, so anyone help would be much appreciated.12 Replies
Project ID:
b5af5fab-625a-4f48-8ec7-3aa80dd451edSame here
it ignores my
RAILWAY_DOCKERFILE_PATH env var
2 people enough to mark this as an incident?Same for me !
Hey, just seeing this. Will raise internally.
If any of y'all have a recent deployment that respected the variable, it'd help me narrow down when the issue started happening.
A fix for now would be to add a
railway.toml file to your codebase with the following:
I'm on a monorepo.
I have several deployments using the same code but the variable RAILWAY_DOCKERFILE_PATH tells for each of them what service to deploy.
Is there any way I can use your fix for my usecase ?
I have same setup as @djodjie with monorepo
Just an update here, I've raise this internally. I'll share an update once I get a response.
I also have a monorepo
This should be fixed now.
@Dylpickle @djodjie @Reilly Sweetland
I’ll check once I get out of bed
works!
Fix confirmed! Thanks