BOOTC-UPGRADE(8)
π
BOOTC-UPGRADE(8) β the bootc-upgrade page, but make it make sense
okay so bestie, this one lives in the System Manager's Manual section 8, and it's literally the glow-up button for your system. buckle up π
β¨ NAME β¨
bootc-upgrade β download and queue an updated container image to apply π¦
πΈ SYNOPSIS πΈ
bootc upgrade [OPTIONS...]
π DESCRIPTION π
Download and queue an updated container image to apply. that's the whole vibe, no cap.
here's the important part though: this does not affect the running system. nope. updates operate in an "A/B" style by default, so your currently-running self is safe and sound while the new one waits in the wings π
a queued update shows up as staged in bootc status. so if you're wondering "did it work??" β go check status, bestie.
π Checking for Updates π
the --check option lets you verify if updates are available without downloading the full image layers. it only grabs the updated manifest and image configuration (typically kilobyte-sized metadata, tiny little snack π), which makes it much faster than a full upgrade. it's giving "peek at the menu before you order" energy.
π Applying Updates π
currently, by default, the update gets applied at shutdown time via ostree-finalize-staged.service. so it kinda just... happens when you leave. iconic behavior honestly.
there's also an explicit bootc upgrade --apply verb which will automatically take action (rebooting, bestie, a whole reboot) if the system has changed.
β οΈ however β in the future this is likely to change, such that reboots outside of a bootc upgrade --apply do not automatically apply the update in addition. so don't build your whole personality around the current default, k? π
π§ Soft Reboot π§
for shared --apply and --soft-reboot behavior, see Soft reboots (check out bootc-upgrades(7)). go read it, it's right there π«Ά
π OPTIONS π
--quietβ don't display progress. silence, but make it β¨intentionalβ¨--checkβ check if an update is available without applying it--applyβ restart or reboot into the new target image π₯--soft-reboot=SOFT_REBOOTβ configure soft reboot behavior- possible values:
requiredauto
- possible values:
--download-onlyβ download and stage the update without applying it--from-downloadedβ apply a staged deployment that was previously downloaded with--download-only--tag=TAGβ upgrade to a different tag of the currently booted image π
π EXAMPLES π
check for available updates:
bootc upgrade --check
upgrade and immediately apply the changes:
bootc upgrade --apply
upgrade with soft reboot if possible:
bootc upgrade --apply --soft-reboot=auto
upgrade to a different tag:
bootc upgrade --tag v1.2
check if a specific tag has updates before applying:
bootc upgrade --tag prod --check
upgrade to a tag and immediately apply:
bootc upgrade --tag v2.0 --apply
π¦ SEE ALSO π¦
bootc(8), bootc-switch(8), bootc-status(8), bootc-rollback(8) β the whole friend group, go say hi π
β VERSION β
v1.17.1 β yeah that's the version, and that's the tea β
and that's the whole page, bestie!! you ate this. go forth and bootc upgrade responsibly. mwah ππβ¨ periodt.
BOOTC-UPGRADE(8) β part of the System Manager's Manual, version v1.17.1. bye babes!! π«Ά
π¦ where this page comes from
- fedora 43: bootc 1.17.1-1.fc43 Β· Apache-2.0 AND BSD-3-Clause AND MIT AND (Apache-2.0 OR BSL-1.0) AND (Apache-2.0 OR MIT) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND (Unlicense OR MIT)
- fedora 44: bootc 1.17.1-1.fc44 Β· Apache-2.0 AND BSD-3-Clause AND MIT AND (Apache-2.0 OR BSL-1.0) AND (Apache-2.0 OR MIT) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND (Unlicense OR MIT)
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms