So I took the plunge and installed Fedora Silverblue because of all that immutable buzz. And it’s the most frustrating change I have made in almost 20 years of my distrohopping.
After installing Silverblue I configured it as usual. I installed necessary flatpaks, played with toolbox and distrobox, installed codecs, configured my bluetooth keyboard and other stuff in /etc and /var. Applied some useful tweaks I found on the web and… well… everything works. Nothing to do anymore. No issues. Nothing breaks, no dependency hell, everything runs smooth. I have nothing to tweak, tinker or configure anymore. So frustrating.
Every update is just… meh. Smooth, new, fresh system not affected by my stupid tweaking and breaking. Booooring.
I don’t have to distrohop anymore. If I want other distros I can just install them in distrobox. Other versions of apps? Something from AUR perhaps…? No problem. What’s the point of distrohopping now? Other DEs? I just rebase my system to other images with almost any DE or WM I want without losing data or messing everything up (damn you, UBlue!).
I don’t even have to reinstall the damn thing cause every time I update the system or rebase it to another image it’s like reinstalling it.
Silverblue killed distrohopping for me. Really frustrating.
Only thing I haven’t figured out, yet, is how to install the Private Internet Access client. It uses a
.runinstall script, and it fails when installing viarpm-ostree(tries to write to/etc) and doesn’t like being installed in a Distrobox (needs systemd).But yeah, I’m currently looking at some other options for my main system to drop Windows, and I’m always comparing to Fedora Atomics, now.
Any program with an install script makes assumptions about your system, if it doesn’t work it just isn’t compatible.
Either modify the script, package the software for your distro or find out if someone else has done it.
My first instinct would be to look if it’s in the AUR and install it inside an Arch Toolbox.
I don’t use PIA, but /opt and /etc are both r/w in Silverblue/Kionite
I’ll have to give that a try, then. Doesn’t work on Bazzite.
Yeah, third-party Linux VPN clients are pretty screwed on silverblue, and probably always will be. Especially since when installed in a container, they require being ran in a rootful container with selinux labeling disabled to enable direct access to /dev/net/tun, and as you’ve quickly found out, most of those weird bash based installers haven’t adapted. It’s best to use generic VPN configs through your DE atm.
why not use fedora’s built-in openvpn client and just add the pia info? That should likely work. https://helpdesk.privateinternetaccess.com/guides/linux/linux-installing-openvpn-through-the-terminal
or built-in wireguard client? https://helpdesk.privateinternetaccess.com/guides/linux/alternative-setups-4/linux-manual-connection-scripts
I do use OVPN. PIA didn’t have a standalone WG config apart from their client when I last checked, so I’ll have to look at that second article and see if it’s workable, because the other issue is ease of use (I’m not the only one using it, you see).
Thanks for the info, though! Might solve my last hangup.
you can unlock the file system, don’t remember how tho
Wouldn’t help, because any changes I make would be wiped out on the next update (plus it kind of defeats the purpose of an immutable system). I don’t want to go down that road, primarily because the maintenance needs to be as easy as clicking a button (I’m not the only user, so ease of use is necessary).
The better option would be to have it live in the filesystem overlay, but I can’t seem to get that to work. It’s possible that it could be a flatpak, as ProtonVPN has their client as a flatpak, but PIA doesn’t seem all that interested in throwing any bones to Linux users.
you can unlock your /usr with rpm-ostree usroverlay
Oh, hmm. I’ll have to look at that. I didn’t know you could unlock the overlay for specific folders