Updates and Reboots
cache22 follows the bootc atomic-update model: a new OS image is staged in a separate slot, and the next reboot applies it. Rollback returns to the previous slot.
The main commands:
| Command | Purpose |
|---|---|
cache22-update |
Fetch and stage the next image. |
cache22-reboot |
Apply the staged image. Auto-selects from two reboot paths. |
cache22-changelog |
Show the package-level diff between booted and staged. |
cache22-autoupdate |
Schedule unattended cache22-update runs. |
cache22-autoreboot |
Schedule unattended reboots after auto-updates. |
cache22-rebase |
Switch between cache22 variants or pin to specific images. |
Pages in this section:
- Two Reboot Paths. How cache22-reboot picks between kexec and full reboot.
- cache22-update. Fetching and staging updates.
- cache22-reboot. Applying staged updates with the right strategy.
- Auto-Update and Auto-Reboot. Hands-off daily updates.
- cache22-changelog. Inspecting a staged update before applying it.
- Pinning and Rollback. Sticking to a specific build, reverting on failure.