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.
Congratulations. You have completed Linux. Please prepare a usb installer for Haiku to move on to the next step of your jouney.
You got me so good. Been using fedora for a few years now and I’ve been hesitant to hop to silverblue but now, after reading your issues with it I might just have to stay away. I can’t imagine a world of painless updates and rebasing smoothly. If I don’t have things to troubleshoot what else am I gonna do on my PC!
Oh man. I’m so sorry for your loss. May your system break at some vague point in the future in a way that is nigh impossible to diagnose and that no one else seems to have experienced. Godspeed, you unwillingly content penguin!
that the thing, if it breaks, the roolback is there or simply rebase without merging /etc, so basically a factory reset
Is this a First Linux-World Problem? :D
To me, I like how clean and coherent GNOME looks like, but what I don’t like about it, is how hostile it is in regarding of themeing/coloring.
Aren’t a lot of these issues due to gtk not being as theme friendly as Qt?
It is my understanding that a lot of thought and care is put into the design language and appearance of applications and frameworks. However the same level of consideration is not usually afforded to skins and themes, which are often released an never updated again. This can cause usability issues and sometimes even breakages. Of course, people are free to do as they please with their computers.
Yeah I get the rational, and that DEs shouldn’t theme them apps but I want to have some sort of customization (not just an accent color).
Thank you. I feel like I’ve found a new way to respect developers that I hadn’t considered before.
I don’t support that some want to push their own theme. Just use the provided theme. You may create your own custom theme but that should be able to be used everywhere. App icons can be part of a theme.
Screw that.
Yeah. My guess is that for every meticulously hand crafted ui, there’s 10 that just go with the default. If a user wants an icon pack where🤘means home, they’ll be perfectly fine with navigating your application.
Developers can always include an option to disable styling if that would severely break the ui. But personally, I’d rather use a application that looks roughly like every other one in the system, than one that’s so specifically designed that it doesn’t.
Have you tried Gradience?
feels like this post was sponsored by Anne Hathaway
Agreed. Been super boring and stable on Aurora.
And good resources on how to learn to use Toolbox properly?
Toolbox create Toolbox enterNow you have a standard Fedora command line system that shares your home folder but otherwise has its own filesystem.
There’s more options (like using other distro’s), but it’s really not complicated.To install CLI stuff that needs to access your host system’s root files, use rpm-ostree (but if you need a lot of that, use a non-immutable distro instead).
I actually use neither anymore. My stuff I want to edit is in home, most programs I use are GUI and I have no need to tinker on this system, cause it just works.
TL;DR Don’t (unless your needs are really basic or you really don’t want to layer more packages)
Distrobox ftw, its website is pretty good to find all its features and it has a neat GUI BoxBuddy too! And also the generic Pods can be useful for more advanced needs.
Extra tip: if you have more time to spend on learning, I think Nix Home Manager will actually be the better solution in the long run, no need to worry about containers breaking in some way after system updates with scattered solutions that are hard to understand and remember, also you get to bring your configuration anywhere
I rebase quite often, its the better distrohopping.
Have a look at Fedora Discuss, interesting things there.
What does rebasing mean in this context? I try to google it, but all I get is git rebase.
Any articles about it that are worth reading? Or if you can explain, that would be neat. Thanks!
Its the same :D
Rebasing refers to an OSTree remote which is like a git repo, but with binaries and producing bootable systems. There are some differences there.
The idea is: there is a remote that has the exact wanted configuration, your system mirrors it. All the package manager does is similar to
git pull.If you rebase, you switch the upstream remote, and your system gets the diffs, downloads them.
The cool thing is, that these updates are atomic, so you stay on the current system and the rebased one is only set as the system you boot in after a reboot. You can still
sudo ostree admin pin 0before rebasing, and your current system will be saved forever to switch back to.Note that /etc is writable so you might still accumulate duplicate or redundant configs.
It’s a command provided by the OS to distrotop between ublue distros. You can basically hop between silverblue, Kionite and Bazzite with a single command.
So, this is only available for Fedora users?
ostree based distros*, the default fedora don’t use ostree so you can’t rebase, bazzite is not fedora but they also use ostree, so you rebase there
I have so much to learn. Last time I was tracking distros and having fun with distro hopping was with Slackware 7, I think.
What is ostree? What is bazzite? Time to google stuff.
I’ve been running Bazzite based on silverblue on my desktop for remote gaming and dockering. Everything was amazing until I started doing some mid-level docker stuff because of the rigidity of the distro.
Podman largely works but since it’s rootless it won’t have access to mounted drives easily due to SELinux.
Mounting a drive automatically wasn’t intuitive either and I ended up editing the /etc/fstab manually.
Setting up a swapfile was also tedious, I needed more than 8GB so I made a 32GB swapfile but I still had to run a sudo command on startup since I’m not really confident with creating a systemd service on an immutable distro.
All in all I should have just gone for Nobara or a regular Fedora but that’s because I have a really edge use-case.
That being said I still highly recommend it. It’s stable, easy to “rebase-hop” and everything just works well and it’s very stable. I’d recommend it for pretty much anyone unless you’re going to do some heavy self hosting with multiple HDs.
deleted by creator
I’m still getting things set for Silverblue to be my baremetal hypervisor distro on my laptop. And by that, I mean giving up on Incus, setting up libvirt, and… everything is working like it should. I wasn’t expecting that. Now, I’ve got to find something else to do with my time.
What’d you dislike about Incus that libvirt does easier? I’m on a similar trajectory as you. I have Incus on Debian but I am transitioning to IoT for that machine. I kinda like Incus. I want to attach USB devices to a couple of my containers, it was a learning curve but eventually worked out alright.
For me, I think it’s just not ready for non-Debian distros yet. The docs and packages just aren’t up to parity. I like a lot about Incus and its general direction but libvirt and virt-manager are fully functional at the moment. Passing through devices with virt-manager is dead easy.
But well, if that helps, look at the bright side: while it’s true that it’ll almost never give you problems, I think it’s true that the time the problems will happen, they will be pretty hard to solve, so it might pretty bad. That’s great, isn’t it?
Don’t tell me that this thing just cannot breaks. If that was even possible, that’d be tremendously evil.
I’m trying to make a TPM chip work out of curiosity and it has been frustrating. Does that help?
bro, trust me i tried to break it, i booted without kernel parameters, my system didn’t even had a root partition, shit was craze, and it didn’t have a /home, rolled back just fine
-rebase from different fedora versions, i couldn’t even login because of kernel versions(yeah even trying to login as root didn’t work)
but, i read a history that happened a bug in ostree, in the early days, and the devs needed to ask the users to fix it manually, but was when in the start of silverblue
That really sucks, sorry to hear that man. It seems honestly pretty bad and I really have to stay away from this distro.
Only RedHat could have conceived something this evil. Of course is RedHat, who else could it have been?
But…!
but, i read a history that happened a bug in ostree, in the early days, and the devs needed to ask the users to fix it manually, but was when in the start of silverblue
This. This is really giving me hope. It kind of confirms what I was saying too. You see? It almost never breaks. But when it breaks, oh man! It breaks very hard indeed.
Never give up mate, that thing is gonna break somehow, sooner or later. It has to.
found it lol, apparently was a grub issue not ostree one, the last thing standing between a full atomic system, grub lol
Wow I was so confused while reading this haha, got me good there! Happy to hear its working as expected :P
Silverblue killed distrohopping for me. Really frustrating.
Then kill it. Distrohop again.
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.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.
you can unlock your /usr with rpm-ostree usroverlay
you can unlock the file system, don’t remember how tho
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 don’t use PIA, but /opt and /etc are both r/w in Silverblue/Kionite
