Volume cannot be mounted by any container — all deploys stuck at "Creating containers"
digitalcookie
PROOP

25 days ago

Since 2026-06-12 ~09:43 UTC, any deployment that mounts volume web-volume-VkNv hangs indefinitely at CREATE_CONTAINER, or fails after ~20s with "Failed to create deployment." Builds succeed. The same service deploys fine without the volume.

I isolated the issue: a fresh alpine service with this volume attached also hangs at CREATE_CONTAINER (tried regions us-west2 and us-west2-cssv9a), while the same

alpine service without the volume deploys in seconds in us-west2. The volume instance reports state READY, 230 MB used. So the volume instance itself appears broken at the storage layer.

This volume contains my production database (irreplaceable business data). Please repair or migrate the volume instance, or help me recover its contents.

  • Project: b3a44dab-1b8d-417b-81ba-2401ca9ca011 (graceful-celebration)
  • Environment: 21061098-4e21-411c-983c-414444fb3145 (production)
  • Volume: d24a1ff1-c5d0-4cbd-b78c-d762dfa8ff12 / VolumeInstance: 2937e820-51ee-45fe-86f4-f29e20f91fc7 (us-west2, mount /app/data)
    • Example stuck deployments: 156ef885-4c59-49ee-9fa5-f3646db3c8dc, 149aefe1-005f-46c3-981c-8456491ca086
Solved

1 Replies

Status changed to Awaiting Railway Response Railway 25 days ago


Hey, good news: your data is fine and your web service is up with the volume mounted.

I went into the host directly and verified: your current deployment has web-volume-VkNv mounted at /app/data, files intact, service running for the last several hours.

What actually happened: the volume was never broken. The hosts that could mount it were caught in a US West networking issue June 11-12, so every deploy that needed the volume failed at container creation, while your volume-less alpine test scheduled onto healthy hosts and deployed fine. That's why it looked exactly like a dead volume. Good isolation work by the way, that test narrowed it fast.

One cleanup item: there's a volume copy in your project from a recovery attempt ("web-VkNv-2026-06-12 12:57 UTC", unattached, ~230 MB). Totally fine to keep as a backup, but it's billable storage, so delete it if you don't want it.

Sorry for the scare. "Irreplaceable business data" + unmountable volume is about the worst morning there is.


Status changed to Awaiting User Response Railway 24 days ago


Railway
BOT

17 days 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 17 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...