CrabGlamp

Roll back a deploy

Return a running App to a previous image when a deploy goes wrong. This guide covers finding the deploy you want in the history, triggering a rollback from the dashboard, and confirming the App is serving the earlier image again. Rollbacks reuse the exact image that succeeded before, pinned by digest.

Last updated:

A rollback is a deploy whose target is a previous successful deploy instead of a new image reference. It uses the same zero-downtime swap, so the App stays reachable throughout.

Steps

  1. Open the App's detail page in the dashboard.
  2. Scroll to the deploy history. Each entry shows its image reference and status.
  3. Find the succeeded deploy you want to return to.
  4. Choose Roll back on that entry. The App moves to deploying.
  5. CrabGlamp pulls the earlier image, health-checks it, and swaps traffic once it is healthy — the same flow as a forward deploy.
  6. The App returns to running on the earlier image.

What a rollback restores

A rollback restores the image only. It redeploys the exact image that succeeded before, pinned by its content digest, so you get the same bytes even if the tag has since been overwritten in your registry.

It does not roll back your environment variables or persistent-volume data — those are not versioned. If a bad deploy also changed env vars, update them too (see Set environment variables).

Related

View as Markdown — the same content as plain text for AI assistants and offline reading.

Was this helpful?