bootc
No written verdict yet. Here is what commenters said.
5recommend
1warn against
Dec 3, 2025first mention
Jun 4, 2026latest mention
Why people recommend it
“rpm-ostree is being phased-out in favor of bootc[1]”
switched from rpm-ostreeon “Making Debian or Fedora persistent live images”
“I recently converted my NAS from plain Debian to a custom bootc image based on Fedora 43 and I love it”
Show 2 more
“I recently wrote about using it in”
“bootc and OSTree are both very neat”
Caveats and dissent
“they are both more complex _and_ less capable than nixos.”
Often compared with
Who recommends it in their own words
Threads where it came up
- Bootc and OSTree: Modernizing Linux System Deployment 6 mentions
- Pocketblue - Fedora Atomic for Mobile Devices 2 mentions
- Making Debian or Fedora persistent live images 1 mention
- Debian must ship reproducible packages 1 mention
- Building a custom NAS/homeserver with Fedora CoreOS 1 mention
- Mount Mayhem at Netflix: Scaling Containers on Modern CPUs 1 mention
Data: bootc.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 16
“rpm-ostree is being phased-out in favor of bootc[1]”
“bootcrew have bootc Containerfiles for Debian, Ubuntu, Arch, and openSUSE”
“I recently converted my NAS from plain Debian to a custom bootc image based on Fedora 43 and I love it”
“This is nice for things like bootc [0] that are deployed on the "edge"”
“Bootc (osbuild) builds VM and native machine images from Containerfiles:”
“they are both more complex _and_ less capable than nixos.”
Ironically the first implementation of ostree required an HTTPS server to serve the ostree commits, allowing a much smaller subset of what's needed to be transferred. However that became an adoption hurdle since it required unique infrastructure. Ostree switched to using containers because zstd allows compressed chunks now rather than the old all-or-nothing image layers, and the existing widespread container image re
“I recently wrote about using it in”
“not completely separated from bootc and ostree”
“bootc and OSTree are both very neat”
“It is not, the future is currently pointing to composefs:”
“Quote from https://bootc-dev.github.io/ tells me that bootc is using OCI as a delivery format”
“This is based on bootc”
Yes, and I think we're already seeing that in the general trend of recent linux work toward atomic updates. [bootc](https://developers.redhat.com/articles/2024/09/24/bootc-getting-started-bootable-containers) based images are getting a ton of traction. [universal blue](https://universal-blue.org/) is probably a better brochure example of how bootc can make systems more resilient without needing to move to declarative
“bootc can by itself completely replace rpm-ostree”
“the bootc documentation which is the container runtime running at the core of Aurora”