February 27, 2026
Images vs Trees: pick a side
Bootc and OSTree: Modernizing Linux System Deployment
Linux gets save‑game updates, but fans feud over the next big standard
TLDR: Linux is moving toward image-style system updates with OSTree and Bootc, making rollbacks and consistency easy. Commenters are split: some love the “save point” vibe, while others say the future belongs to a new systemd-backed standard, sparking a battle over which approach will win.
The author bails on old-school install tools after the HashiCorp licensing drama and lands on Fedora Silverblue, using OSTree — basically Git‑style “save points” for your whole computer — plus Bootc to ship entire system images like apps. That means easy rollbacks, less breakage, and a dev laptop that feels like it has an Undo button. Tech folks swooned… then the comments kicked off.
Borealid cheers the “one format for everything” vibe, wanting virtual machines and containers to speak the same language — and even backups stacked as image layers in the same online warehouses. But they drop a spicy line: they’re “not sure ostree is going to be the final image format,” stirring worry that today’s hero could be tomorrow’s legacy. Then pojntfx rolls in with a plot twist: the cutting edge (GNOME OS, KDE Linux) is “converging” on a new systemd-backed standard from the UAPI Group, pointing to specs here: link. Translation: the cool kids may already be moving to a different playbook.
So it’s Team Tree (OSTree snapshots) vs Team Image (systemd’s new standard). Jokes fly: “Press CTRL+Z for your OS,” “Version control your life,” and “Choose your fighter: Bootc vs UAPI.” The mood? Excited, skeptical, and very popcorn-friendly.
Key Points
- •The author moved from Packer-built VM images due to HashiCorp’s licensing changes and sought a more suitable approach for developer machines.
- •After challenges with NixOS, the author migrated to Fedora Silverblue to gain an immutable system while retaining a familiar Linux experience.
- •OSTree is described as “Git for filesystems,” providing versioned, atomic deployments of complete system snapshots with easy updates and rollbacks.
- •OSTree’s storage uses ComposeFS and EROFS for integrity, deduplication, and LZ4 compression, with system versions stored under /sysroot/ostree/repo/objects and identified by hashes.
- •OSTree is used beyond Silverblue, including in Fedora CoreOS, Endless OS, and Podman VMs on macOS and Windows; an example image (uBlue OS Bluefin DX) illustrates tracked versions and digests.