FerryDocs
ArchitectureDeploy pipeline

Restarts and rollbacks

A restart and a rollback are deploys that use an image again and build nothing.

Edit on GitHub
Earlier deployits imageLive deployits imageSettingsthe current onesNew deploytrigger: restart

A restart runs the image of the live deploy.

1 / 3
ImageOf the live deployOf an earlier deploy
Settings, limits, environmentThe current onesThe current ones
RuleThe engine finds the live deploy when the restart runs, not when it enters the queue.The target was live: its status is live or deactivated. Its image must still exist (see --keep-images).

Why the restart rule matters

A restart that waits in the queue behind another deploy does not undo that deploy. It restarts the new live deploy.

A restart is how a change of variables reaches the containers that run.

For the user view, see Restart a service and Roll back.

On this page