Updates, the comic

New editions overnight, the old one kept.

The same kitchen as the other comics, at four in the morning. A van brings new editions of the recipe books. The chef hands them out one cook at a time, keeps the old ones, and swaps back the moment a cook cannot manage.

1 A delivery at four

Updating is turned on per compose project or per cook, never for everything at once. The database on your home server and a recipe you wrote yourself do not want the same treatment.
New books for Ben,not for Ada.I’m thedatabase.
At a moment, not an interval: four in the morning by default. An update should not drift an hour later every day until it happens at noon.
04:00
A laptop that was off at four updates when it wakes up. Off for a week? It updates once, not seven times.
Closed all week?Just the latest.Once isenough.

2 Back to what worked

Before the new edition goes on the shelf, the old one’s id is written down and the book itself is kept.
I’ll keepthe old one.New edition!
Is the cook not back within five minutes, or does the health check never turn healthy? The old id goes back on the name, and the cook starts again with the book that worked.
Five minutes.Back to the old one.This recipedoesn’t work!
One cook at a time, and after the first rollback the round stops. If tonight’s edition takes down half the kitchen, you want the chef to stop, not finish the list.
One went back.That’s it for tonight.

3 Decisions you make awake

Changed the compose file since those cooks were made? Recreating would roll out your changes too, and that is a decision you make awake. The chef leaves it alone.
The menu changed?Not at night.
One notification in the morning, “2 updated, 1 rolled back”, not one per cook. Waking up to five only teaches you to dismiss them. The results stay on the dashboard for a day, and in the diary.
1Just onenote?2 updated,1 rolled back.
In Docker Client MX: updates per project at the hour you pick, the old image kept, and back to it if the new one does not come up. Update now takes the same path, so you can watch it once before you trust it overnight.
THE END

The cheat sheet

Every picture above, in Docker words.

A new edition of the book
A newer image under the same tag
New books for Ben, not Ada
Updates per compose project or container
The van at four
A moment you pick, 4 am by default
Closed all week, one delivery
A missed night, caught up once
Keeping the old edition
The old image id, remembered and kept
Back to the old one
A rollback: not up in five minutes, or never healthy
That’s it for tonight
The round stops after the first rollback
A menu that changed
An edited compose file, left alone
One sentence in the morning
One notification for the whole night
Now let the van come at four.
Updates per project at the hour you pick, a rollback when the new image does not come up, and one notification in the morning.