Skip to content

Commit ea554f5

Browse files
committed
switch: Document digests
Came up in chat. Signed-off-by: Colin Walters <[email protected]>
1 parent 51d70f1 commit ea554f5

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

docs/src/man/bootc-switch.8.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,8 @@ A common pattern is to have a management agent control operating system updates
1919
for example, `quay.io/exampleos/someuser:v1.0` and `quay.io/exampleos/someuser:v1.1` where some machines
2020
are tracking `:v1.0`, and as a rollout progresses, machines can be switched to `v:1.1`.
2121

22+
It is also supported to provide explicit digests, as in `quay.io/exampleos/someuser@sha256:9cca0703342e24806a9f64e08c053dca7f2cd90f10529af8ea872afb0a0c77d4`. When you do this, `bootc upgrade` will always be a no-op. In this model, upgrades are then always triggered by further `switch` operations.
23+
2224
## Applying Changes
2325

2426
The `--apply` option will automatically take action (rebooting) if the system has changed after switching to the new image. Currently, this option always reboots the system. In the future, this command may detect cases where no kernel changes are queued and perform a userspace-only restart instead.

0 commit comments

Comments
 (0)