Skip to content
Confirm Docker image rollback and persistent volume safety
chicchocrider
OP

15 days ago

Hello Railway team,

I have a healthy production service with a persistent SQLite volume mounted at /data.

Before deploying an update, I would like to confirm the safest rollback procedure.

Could you please clarify:

  1. Can Railway restore the exact Docker image of my currently active deployment after a new deployment replaces it, without rebuilding the image?
  2. How can I verify that this deployment is eligible for rollback before deploying?
  3. What is the image retention period for my plan?
  4. Will rolling back preserve the existing /data volume and its current SQLite database, including subsequent writes?

I am not experiencing an outage. This is a precaution before a planned production update.

I do not want any changes made to the service at this time.

Thank you!

Solved

1 Reply

Railway
BOT

15 days ago

Yes. When a new deployment replaces your current one, the old deployment is removed, but we keep its image for 72 hours on Hobby. Rolling back within that window restores that exact image, its settings and its variables as a new deployment, with no rebuild. After the window, the rollback option disappears and the only path is Redeploy, which rebuilds from the original source.

There is nothing to check beforehand. The 72 hours start when the deployment is removed, not when it was built, and an image used by an active deployment does not age out. After you deploy, the rollback option is in the three-dot menu on the previous deployment in the service's Deployments tab, and it only appears while that deployment is still inside the window. See Deployment Actions and the image retention policy.

Rollback only restores the image, settings and variables. It does not snapshot or revert your volume, so the /data volume stays attached and the SQLite file rolls back in its current state. Any writes the new version makes, including schema changes, stay in place and the older image will read that data.


Status changed to Awaiting User Response Railway • 15 days ago


Railway
BOT

8 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 • 8 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...