Skip to content
Deploy fails at pre-deploy: "no volume attached" but volume is mounted at /data
gmazzone79-ctrl
OP

a month ago

Service "web" in project "Sviapz Smartcore" (production). Since today ~20:54 UTC every deployment

fails at "Deploy > Pre deploy command" after 1 second with:

"This deployment expects a volume mounted at /data, but the service has no volume attached.

Railway did not create the container."

The volume "web-volume" IS attached to the service, mount path /data (50 GB, EU West), as shown

in the volume settings. The deployment of this morning (~07:51 UTC, same railway.toml, same

Dockerfile, same volume) succeeded. Nothing changed in our deploy configuration since then:

the new commits only touch application code. Three attempts (one from GitHub push, two manual

redeploys) failed the same way. The previous deployment is still serving traffic.

Could you check why the volume attachment is not detected at the pre-deploy step?

We use railway.toml (releaseCommand + startCommand, builder DOCKERFILE).

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • about 1 month ago


hackvhilzan

a month ago

Same issue here. Project "Zarabots", service "Zarabot" (production, EU West). Volume "zarabot-volume" attached at /data. A deployment at ~12:05 UTC today succeeded; since ~20:03 UTC every deployment fails at "Pre deploy command" with the same "expects a volume mounted at /data, but the service has no volume attached" error. No config changes on our side.


chandrika
EMPLOYEE

a month ago

Hey! Thanks for the detailed report. This was caused by a recent change on our side, and we've now rolled it back. Deploys with a volume and a pre-deploy command should go through again, so please redeploy and your volume will be mounted as usual. Your volume and its data weren't affected.

If you detached your volume or deployed without it while this was happening, reply here before redeploying and we'll help make sure nothing written since then gets lost.

Sorry for the disruption, and let us know if anything still fails.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...