yeah. But I also think that the idea of installing a single package being able to break the entire system like that is the underlying problem.
I understand its a last resort but for many people its the ONLY thing they can do. Not every piece of essential software can be run through extremely layered high level flatpaks.
Thatâs just matter of reading the docs and know what you get yourself into when you start layering. You need to check if updates still work. They absolutely should. But can cause errors. Just something to be aware of.
I havenât tried but in this case I believe the .sh scripts that NordVPN provides as official Linux installer probably work just fine if they install in the user profile. And might even update itself. So run once and done. Layering in that case makes no sense.
This is how Koofr works on Linux. Install via the .sh they provide and done. It will keep itself updated.
again there IS no other way. even if I knew what I was getting into I HAD no other option because not every piece of software is some high level super layered flatpak
yes. The sh script pretty much installs a package file using fedoras offical package manager yum. I had to manually install it using rpm-ostree and edit the sh script
NordVPN offers OpenVPN and other types of config files that you can get in your account portal. Those work natively in Gnome Network Manager and no need to install NordVPN software.
Regardless, installing packages on imnutablenisbfine, its just different, just like packages between distro families dont work (Deb vs rpm). For Immutable images, the install process is either use something that works with your user level stuff like Flatpak, Brew, or AppImage, or you build your own custom image on top, with your added packages. Thats how you install packages.
Layering was a bandaid stopgap measure until tooling and process improved.
Finally, it Immutable doesnt work for you, you can easily use a non-immutsble system. CachyOS, Nobara, Fedora itself are all just as capable and are normal distros. Immutable is a completely different paradigm and is also young. It has also saved my ass a few time due to mistakes and Ive been using Linux for decades and am a DevOps Engineer.
You either need to adapt to the immutable way of doing things, or use the many other great options available.
I can also confirm Bazaarâs instability. Tested on three completely different machines (PCs, Laptops), with no overlays (local packages), no VPN (except ProtonVPN occasionally, from flatpak).
So yes, inconsistent crashes, just bombs away, etc.
Like mansioned in the software installation instruction, you can try to launch for example Fedora distrobox, and install NordVPN through .sh in it, if you prefer .sh installation instead of .ovpn direct configuration.
Immutable Fedora Silverblue (on which Bazzite is based on) is the most stable distro I have ever used.
I believe that you should not layer anything on immutable distro. If you really want to, you should either use âclassicâ distribution or build your own with GitHub Actions CI/CD and stuff as was suggested before.
Immutable distros in general are not for people who want to have 101% control over their OS, it is for people who donât want to spend time maintaining their OS. Want to use software that is not available as Flatpak? Then AppImage is the only recommended option (with a major FUSE2/FUSE3 headache thou). If you want to tinker with *anything* on such OS, you should only do it inside Podman container.
This post is related to Bazaar instability. It doesnât matter if itâs a pure immutable image or an image that has layered software. I sort of agree with you about Fedora Silverblueâs stability, but Bluefin, Aurora and Bazzite take stability to a next level. Anyway, Bazaar bombs every once in a while, so it needs a lot of work.
I disagree. Even if you layer stuff, Fedora Atomic gives you protections that traditional Fedora cannot. No easy rollbacks, not as strong protections against configuration drift, etc.
Doing stuff with Github actions is no silver bullet either. That can break too, leading to no updates until you fix it.