a month ago
My service kazi_yangu in project ideal-tranquility (Project ID: 63c56d2c-90d6-41c4-bdb8-198b3a4e6a71) had its container restarted after an environment variable change today (May 21, 2026 around 10:00-11:00 UTC). The service had a SQLite database at /app/prisma/dev.db inside the container with 256 production records that was lost when the container restarted. The previous deployment ID is 781c211c-c898-4299-9aee-0458192f885f. Please can you check if the old container's writable layer still exists on your infrastructure and recover the file /app/prisma/dev.db from it. This is urgent production data.
Pinned Solution
a month ago
You should attach a volume to your service (right click your canvas, add a volume, select your service, and mount it to /data). You should then update your codebase to access the SQLite database from the /data path (eg, /data/database.db).
3 Replies
a month ago
Data stored in the container's filesystem (outside a mounted volume) is ephemeral and does not survive restarts or redeployments. We do not retain old container writable layers and cannot recover files from previous deployments. To persist data like your SQLite database across restarts, you would need to attach a volume mounted at the path where your database file lives.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Data stored in the container's filesystem (outside a mounted volume) is ephemeral and does not survive restarts or redeployments. We do not retain old container writable layers and cannot recover files from previous deployments. To persist data like your SQLite database across restarts, you would need to attach a [volume](https://docs.railway.com/volumes) mounted at the path where your database file lives.
a month ago
What is the best path foward
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Open Railway • about 1 month ago
hoseajonas
What is the best path foward
a month ago
You should attach a volume to your service (right click your canvas, add a volume, select your service, and mount it to /data). You should then update your codebase to access the SQLite database from the /data path (eg, /data/database.db).
Status changed to Solved 0x5b62656e5d • 4 days ago