a month ago
My service has a Volume mounted at /data. My app writes a file there and confirms it exists (e.g. 2188 bytes) before the container stops. On the next deployment, the same volume (same ID, confirmed in Settings) shows the directory as completely empty. This happens on every redeploy. Can you check why data isn't persisting on this volume between deployments?
2 Replies
a month ago
Your volume's mount path is set to /data (with a trailing space) instead of /data. Those are two different paths, so your app is writing to the ephemeral /data directory while the persistent volume is mounted at /data . Update the mount path in your volume settings to remove the trailing space, and your data will persist across deployments.
Status changed to Awaiting User Response Railway • 29 days ago
Railway
Your volume's mount path is set to `/data ` (with a trailing space) instead of `/data`. Those are two different paths, so your app is writing to the ephemeral `/data` directory while the persistent volume is mounted at `/data `. Update the mount path in your volume settings to remove the trailing space, and your data will persist across deployments.
a month ago
changed it removed the space and deployed it again
Status changed to Awaiting Railway Response Railway • 29 days ago
Status changed to Solved Railway • 29 days ago