rpm-ostree
ostree
Our great sponsors
rpm-ostree | ostree | |
---|---|---|
47 | 41 | |
813 | 1,175 | |
2.1% | 3.8% | |
9.6 | 9.5 | |
7 days ago | 1 day ago | |
C | C | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rpm-ostree
-
What do you prefer more and why?
I definitely agree that immutability offers considerable value in regards to improving security. But arguably it's insufficient to pull the win over mutable Fedora due to the losses caused by the inability to install the kernel-hardened package and the lack of UKI (Unified Kernel Image) support.
-
Looking to test out fedora Silverblue. I have only 1 question
Issue: https://github.com/coreos/rpm-ostree/issues/3944
-
What is the difference between Immutable Desktops and non Immutable Desktops?
Oversimplifying might have been the most sensible in this context. However, you might have gone a little bit too far as your description fits only NixOS, Guix and distros that utilize rpm-ostree.
-
Universal Blue is a new paradigm for the Linux desktop and it's brilliant
here's the documentation of ostree (the package manager)
-
Fedora Silverblue 38: rpm-ostree crashes
Now... this was VERY alarming to say the least, so I went online and did indeed find an issue on GitHub.
- Fedora Linux 38 released!
-
The New website is here, with modern UI. And getfedora.org redirect to fedoraproject.org with fresh look.π
And there are still some issues with layering. Some packages that don't behave or follow standards will modify files in /usr/local, which isn't supported, so you simply won't be able to install them on Silverblue. I think it's the same for /opt as well. (https://github.com/coreos/rpm-ostree/issues/233) This means it fundamentally can't do everything Workstation can, which is unfortunate.
-
Flatcar Container Linux
ublue is based off of fedora and rpm-ostree, which is what "CoreOS" is today.
What happened was old school CoreOS was A/B partition based: https://github.com/coreos/docs/blob/master/os/sdk-disk-parti...
My memory is hazy but here's how I remember it: After Red Hat acquired CoreOS they rebased the entire thing around rpm-ostree, which is the CoreOS people know today: https://coreos.github.io/rpm-ostree/
At the time there was some anxiety in the community as to what would happen, as there was no direct upgrade path from old CoreOS to new CoreOS. Theoretically if we all believed the kool-aid we were drinking it's just a redeploy, no pets!
Kinvolk came along, forked it, and made Flatcar Linux, which kept the A/B partitioning system, and more crucially, let you just change a config file and all your old CoreOS nodes would just move to Flatcar and then you were good to go. So now if you wanted to stay on the system you were comfortable with you could just use Flatcar. If the composability of rpm-ostree attracted you then new CoreOS have you covered. Red Hat deserves a hat tip here because in their documentation/blog they explicitly mentioned Flatcar as an option for people who wanted to stick with what they know, which I thought was cool and how I discovered it!
Later on Microsoft acquired Kinvolk and and then people raised eyebrows. I have not checked in a while but the folks involved continued to do their thing and run it like a good OSS project, hold public meetings, all that stuff.
I use both and they're both high quality.
-
Immutable Linux Distributions for Those Looking to Embrace the Future
Whenever I was looking at using CoreOS, I was somewhat disheartened that automatic reboots weren't built in: https://github.com/coreos/rpm-ostree/issues/2831. Has this changed? I know zincati has maintenance window support, which would also be nice to have.
-
[HELP] AMD REST BUG
Doesn't look like it https://github.com/coreos/rpm-ostree/issues/1091
ostree
-
NixOS Reproducible Builds: minimal ISO successfully independently rebuilt
Ansible makes mutable changes to the OS, task by task.
Nix is immutable. A new change is made entirely new, and only after the build is successful, all packages are "symlinked" to the current system.
Fedora Silverblue is based on ostree [1]. It works similarly like git, but on your root tree. But it requires you to reboot the whole system for the changes to take effect. Since Nix is just symlinked packages, you don't need to reboot the system.
More detailed explanation here [2].
[1]: https://github.com/ostreedev/ostree
[2]: https://dataswamp.org/~solene/2023-07-12-intro-to-immutable-...
- Can't install from flathub
- hello guys everytime i intall a flatpak on fedora this error always happnes how do i fix it
-
PSA: Flatpaks are currently broken on Fedora. Here's a temporary solution.
This one is for the ostree bug currently ongoing: https://github.com/ostreedev/ostree/issues/2900
-
flatpak issue on fedora 38 kde
This sounds related to the ostree bug.
- ostree-system-generator failed with exit status 1 on every boot after update.
-
What do you prefer more and why?
I definitely agree that immutability offers considerable value in regards to improving security. But arguably it's insufficient to pull the win over mutable Fedora due to the losses caused by the inability to install the kernel-hardened package and the lack of UKI (Unified Kernel Image) support.
-
Question about immutability
Other hardening guides mention a Unified Kernel Image as another measure to further improve security. Unfortunately, once more, this is (currently) not supported on Fedora Silverblue. I haven't seen it being done on openSUSE Aeon either. Though, once again, I'd love to be corrected!
-
Does an immutable system really provide enhanced security?
The fedora crew is working on it through ostree though, so both fedora Silverblue and flatpak will be getting it (as well as true immutability) in the future: https://github.com/ostreedev/ostree/issues/2867
-
Silverblue/ Kinoite - real-life shortcomings?
Aside from what has already been mentioned, Unified Kernel Image isn't supported (yet).
What are some alternatives?
vscode-remote-release - Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.
apt2ostree - Build ostree images based on Debian/Ubuntu
openvpn-install - OpenVPN road warrior installer for Ubuntu, Debian, AlmaLinux, Rocky Linux, CentOS and Fedora
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
cxx - Safe interop between Rust and C++
flatpak - Linux application sandboxing and distribution framework
tectonic - A modernized, complete, self-contained TeX/LaTeX engine, powered by XeTeX and TeXLive.
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.
distrobox - Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution youβre more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
mkosi - π½ Build Bespoke OS Images
com.unity.UnityHub
pkg2appimage - Tool and recipes to convert existing deb packages to AppImage