main
rpm-ostree
main | rpm-ostree | |
---|---|---|
14 | 47 | |
446 | 822 | |
5.4% | 2.2% | |
9.0 | 9.6 | |
1 day ago | 6 days ago | |
Shell | C | |
Apache License 2.0 | 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.
main
-
Issue with updating Fedora 39 silverblue
Best place to start is to get rid of all the layered packages (RPMFusion) on top of the immutable image then swap to the ublue-Nvidia images that have all the codecs and Nvidia drivers built into the image itself.
-
Making the switch - what are the gaps?
If you're using Nvidia I'd recommend using Fedora Kinoite with the ublue-Nvidia image that comes with the Nvidia drivers pre-built in. That eliminates a big chunk of issues with their drivers which is just building the damn things. AMD and Intel drivers are built into the kernel and require zero effort.
-
An Overview of Nix in Practice
What you are looking for is UBlue, https://github.com/ublue-os/main.
It's a variant of Silverblue with Nvidia drivers built in.
-
Are there any major sacrifices you make to play on Linux over Windows?
If you're using Nvidia, then install using the ublue Nvidia image which has the drivers built in, cause they can be a prick to manage otherwise.
-
Introduction to Immutable Linux Systems
What these sort of introductions to immutable always fail to consider is the other side of the coin, image-based. I'm working on https://universal-blue.org/ along with many people much more skilled than me. We build OCI container images on top of vanilla Fedora Silverblue & many other editions with different desktops. Those images can then be booted to (or rather rebased to) using rpm-ostree. This is a more robust way of extending the system than layering, and the same changes can be easily benefited or inherited from by anyone. You can even make your own image really easily!
I think that VanillaOS and SUSE are working on similar things, but we're not an OS project, just a downstream from Fedora. Fedora's full support is underway but with what's already working perfectly our methods are already IME some of the most robust and easy ways of delivering Nvidia drivers for example.
- Again? :(
- Troubleshooting Nvidia driver installation
-
I want to reinstall Fedora with proper NVidia Drivers. Please guide!
Download: https://github.com/ublue-os/main/releases/tag/v1.1.8
- Video thumbnails doesn't work in fedora silverblue 38
- What are some post install tips/commands yall would recommend for f37 workstation running on a ThinkPad x280 (mostly on battery)?
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
What are some alternatives?
ublue - A familiar(ish) Ubuntu desktop for Fedora Silverblue.
ostree - Operating system and container binary deployment and upgrades
bluefin - An interpretation of the Ubuntu spirit built on Fedora technology
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.
nvidia - Fedora variants with built-in Nvidia drivers
openvpn-install - OpenVPN road warrior installer for Ubuntu, Debian, AlmaLinux, Rocky Linux, CentOS and Fedora
podman-appimage - Podman AppImage: A portable tool for managing OCI containers and pods.
cxx - Safe interop between Rust and C++
ca.dcloud.ICAClient - Install Citrix Workspace + HDX RTME as a Flatpak application
tectonic - A modernized, complete, self-contained TeX/LaTeX engine, powered by XeTeX and TeXLive.
layering-examples
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