a month ago
Deployment 35516dbb-3b1c-4e7e-8f43-fec6e22ac3f3 for service 33e69af9-87a7-4c73-86a2-5a493f52a742 is repeatedly failing with a builder mismatch.
Railway is reading and resolving railway.medusa.toml correctly (builder = DOCKERFILE, dockerfilePath = medusa/Dockerfile), but the actual build executes Railpack's shell provider and fails in ~8 seconds. This has reproduced identically across 10+ consecutive redeploys.
The Dockerfile has multi-stage builds with heavy apt and pnpm installs, so the 8-second runtime confirms Railpack is running, not the Dockerfile. The root start.sh was moved to bin/start.sh in the triggering commit, but this did not resolve it.
Please investigate why the resolved Dockerfile builder is being overridden by Railpack at build time.
In the past, I built from a Dockerfile. There are no errors. But the error has happened in the last two days in all environments. My teammate already sent another ticket report about the production environment.
I updated my monorepo as suggested by Diagnosis
- add railway. toml file
- move shell file out of root folder
6 Replies
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
Open your service settings, scroll down until you see "Config-as-code" section and write the file path to your railway.medusa.toml file
mayori
Open your service settings, scroll down until you see "Config-as-code" section and write the file path to your `railway.medusa.toml` file
a month ago
I did it. And nothing success
a month ago
Try redeploy latest commit/redeploy source image
Open your service > Open the command palette (Ctrl-K) > Select Redeploy Source Image or Redeploy Latest Commit
a month ago
I did your suggestion, but the result has not changed and here is reponse from Diagnosis: "Contact Railway support, as this deployment is failing due to a platform-side issue that cannot be resolved through code or config changes. The config file railway.medusa.toml is correctly committed and parsed, the resolved build manifest confirms the Dockerfile builder with path medusa/Dockerfile, and the root start.sh that previously triggered shell detection has been removed. Despite all of this, Railway is running Railpack's shell provider instead of the Dockerfile builder, failing within one second, and this has reproduced across 10+ consecutive deploys with no code or config changes in between."