a month ago
Problem and desired outcome
We want every merge to our staging branch to deploy automatically to the staging environment of the idlox-app service, as it did until earlier today. Since 2026-10-06 ~21:10 CEST, every deployment triggered by a GitHub push fails at "Deploy › Pre deploy command" with "This deployment expects a volume mounted at /data, but the service has no volume attached", even though the Railway UI shows a volume attached to the service at /data. The only thing that has made a deployment succeed is deleting the volume, creating a new one at /data and redeploying; the next automatic deployment fails again. It is still happening. Could you check why these deployments do not find the attached volume, and what we need to change so automatic deployments work again without recreating the volume each time?
Resources and timing
Project: idlox-app
Environment: staging
Service: idlox-app (domain idlox-app-staging-f525.up.railway.app)
Volume currently shown attached to the service: idlox-app-volume-lq75, mount path /data (checked in the volume settings by the user). The volume that existed before today's recreation was named idlox-app-volume.
Build: Dockerfile (railway.json: "builder": "DOCKERFILE", "preDeployCommand": ["node dist/server/migrate.js"]). The service card showed "Waiting for CI", so "Wait for CI" appears to be enabled.
Timeline (UTC, from GitHub deployment statuses reported by Railway for environment "idlox-app / staging"; commits on branch staging):
Commit Deployment created Result
b073916 16:13:25 success at 16:19:47 — last automatic deployment that succeeded
5a85e58 19:10:36 failure at 19:16:06
552344e 19:23:16 failure at 19:28:42
05b8a9e 19:33:25 failure at 19:38:25; redeployed manually 19:44 and 19:47 (see below)
aec78aa 20:20:38 failure at 20:20:39
7835126 20:40:16 failure at 20:45:48 (the Railway deployment page showed 4b8b1a81, 2026-10-06 22:40 GMT+2)
144eafb 21:04:14 failure at 21:09:48
Currently running: the manual redeploy of 05b8a9e from ~19:47 UTC (made after recreating the volume). At 21:10 UTC the app's /api/health answered {"ok":true,"pendingMigrations":0,...}, and around 19:50 UTC the served frontend contained features from that commit. The failing deployments are the later commits listed above, which are not running.
Evidence and attempts
Error shown under "Deploy › Pre deploy command" (user screenshots, same text on several deployments):
This deployment expects a volume mounted at /data, but the service has no volume attached. Railway did not create the container: it would have run without the volume, and data written there is lost on the next deploy. Attach a volume at /data, or remove the mount, and deploy again.
Railway's diagnosis panel on the same deployment: "Diagnosis › Infrastructure Error — Check the Volumes view for the staging environment and confirm the volume is attached to idlox-app at /data, then redeploy. The build succeeded, but Railway stopped the deployment before creating the container because it found no volume attached at /data, even though the service config lists that mount."
What was actually tried, and what happened:
User checked the volume settings: mount path is /data and the volume is shown attached to idlox-app. Deployments still failed.
User ran a manual deploy of the latest commit (Ctrl+K → "Deploy latest commit") with the original volume: it failed with the same error (reported by the user).
User deleted the volume and created a new one (idlox-app-volume-lq75) attached at /data, then redeployed: the deployment succeeded (~19:47 UTC; the app came online).
The next deployments triggered by merges (aec78aa, 7835126, 144eafb) failed again with the same error, with the new volume still shown attached.
status.railway.com showed no incident at ~21:15 UTC.
The repository does not declare any volume (no volume settings in railway.json or the Dockerfile). The application only reads RAILWAY_VOLUME_MOUNT_PATH at runtime to decide where to store uploaded files; the failure happens before the container is created, so the application code does not run.
5 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
I have the same issue please help!
a month ago
Same here!
a month ago
Same issue, started about an hour ago!
a month ago
Hey! Really sorry about the trouble today. This was caused by a recent change on our side, and we've rolled it back, so automatic deploys should work again without recreating the volume.
One important thing: your original volume, idlox-app-volume (about 790 MB), is still intact, but it's scheduled for permanent deletion on Oct 8 at 19:46 UTC because it was removed while you were troubleshooting. The volume attached to idlox-app right now is empty. To get your data back, cancel the deletion of idlox-app-volume in the idlox-app project (from the deletion entry in the project's Activity feed, or the restoration link emailed to workspace admins), attach it to idlox-app at /data in place of the empty one, and redeploy. If you get stuck on any of that, reply here and we'll help before the deadline.
If you're seeing the same error on your own service, redeploying should now work.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Quick reminder: your original volume, idlox-app-volume (about 790 MB), is still scheduled for permanent deletion on Oct 8 at 19:46 UTC. If you haven't restored it yet, cancel the deletion in the idlox-app project (the deletion entry in the Activity feed, or the restoration link emailed to workspace admins) before then, or the data on it will be gone for good. Reply here if you'd like a hand.
Status changed to Solved polakoidlox • about 1 month ago