Skip to content
Deploys fail at "Pre deploy command": "service has no volume attached" - but the volume IS attached (/data, Ready)
vardan8420-bot
OP

a month ago

Since 2026-10-06 20:52 UTC every deployment of service marketplace-wht-am (project elegant-enthusiasm 07f2f268-9a73-48e5-a1ab-c31c875f88db, environment production d5918387-f7bd-4f8d-994f-8508ecd16df1, service 48a8af0c-4c08-49d3-9cc7-9bf55f655532) fails after a successful build and image push, at the step "Deploy > Pre deploy command (00:01)", with:

"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."

But the volume IS attached: railway volume list and the dashboard both show marketplace-wht-am-volume (40f32792-db1b-48ae-9265-9ca86fd0cbc8) attached to this service, mount path /data, Status Ready, 86 MB / 5000 MB used.

Failed deployments: 10e8e06f-3c31-4bb2-8249-2e05b401a32d (20:52 UTC), 6bb4eb16-593a-4617-b62b-af731c986e31, dd0b2730-1e05-4f2d-a512-98e844a11b91, 6d02fdcf-e9dd-4246-8693-5cfeb01bcad9, 44469561-7d63-44e0-8d11-6182870fa015 (21:56 UTC), and a Redeploy from the dashboard, 22dae935 (2026-10-06 22:35 UTC) - all identical. Deploy logs of the failed deployments are empty.

The last successful deployment 5b050a50-959b-4dda-a3ea-ae46a8456dd4 (2026-09-29 16:01 UTC) used the same /data mount and the same service settings (Dockerfile builder, healthcheck /api/health, pre-deploy command prisma migrate deploy, europe-west4, 1 replica). No Dockerfile, package.json, prisma or Railway config changed since then; a documentation-only commit fails the same way. The previous deployment is still online and serving.

The workspace invoice that failed on Oct 3-4 was paid on 2026-10-06 21:05 UTC (receipt #2354-1729); deployments after the payment fail identically.

Could you check why the pre-deploy step does not see the attached volume, and what we should do so deployments go through again? We would prefer not to detach the volume, since it holds uploaded files.

Solved

3 Replies

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


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


vardan8420-bot
OP

a month ago

Thank you. The volume was not detached and nothing was deployed without it: railway volume list showed marketplace-wht-am-volume attached to the service at /data, Status Ready, 86 MB / 5000 MB used, at 22:21 UTC and 01:14 UTC and 04:33 UTC (2026-10-06/07), and no volume change was made on our side. Our only action was one Redeploy from the dashboard at 22:35 UTC on 2026-10-06 (deployment 22dae935), which failed with the same message - that was before your rollback. We will redeploy from the dashboard now and report the result here.


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


vardan8420-bot
OP

a month ago

edeploy from the dashboard succeeded - deployment 7dcc1116-b63c-4948-b054-6bb390f4bd27 (commit b687193e) is ACTIVE since 2026-10-07 04:46 UTC with the volume mounted at /data. Thank you for the quick fix.


Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...