You might be absolutely correct on that.
Though, I do wonder what would prevent a stateless system accompanied by a healthy dose of integrity tests from pulling this off.
You might be absolutely correct on that.
Though, I do wonder what would prevent a stateless system accompanied by a healthy dose of integrity tests from pulling this off.
FWIW, some (perhaps even most/all) uBlue derivatives actually do automatic major version updates. Though, thanks to the bootc-model, they’re dealing with a whole lot less state(/moving parts); hence smooth updates are somewhat expected. The built-in rollback functionality doesn’t hurt either.


Yup, Bazzite is one of uBlue’s images.


My two cents: do yourself a favor and switch to one of uBlue’s images. See: https://ublue.it/
As for the why: while Fedora has put a tremendous efforts into making Fedora Atomic possible and continues to have ambitious goals regarding it, the fact that on the latest major release, a serious regression for at least one of the atomic images was not considered a blocker, showed to all of us that they aren’t as serious about it, at least at this point, as one would like or love to see.
The project has been relatively stale in the last couple of years. And I would argue that were it not for bootc and the whole ecosystem of derivatives that it has made possible, there would have been very little to be positive about (momentum-wise).
By contrast, the uBlue images are actively trying to solve issues and problems that the model has. This has led to it being a very polished experience with a great community around it that’s very actively engaged and that tries to be helpful.
All in all, take it from a Fedora Atomic user of almost four years that the uBlue side of things is definitely a whole lot greener.
Interesting. If you’ve used this on Linux, could you share your experience with and thoughts on it?