ansible-libvirt-microos VS ublue

I've been using a 3 nuc (actually Ryzen devices) k3s on SuSE MicroOS https://microos.opensuse.org/ for my homelab for a while, and I really like it. They made some really nice decisions on which parts of k8s to trim down and which Networking / LB / Ingress to use.

The option to use sqlite in place of etcd on an even lighter single node setup makes it super interesting for even lighter weight homelab container environment setups.

I even use it with Longhorn https://longhorn.io/ for shared block storage on the mini cluster.

If anyone uses it with MicroOS, just make sure you switch to kured https://kured.dev/ for the transactional-updates reboot method.

I'd love to compare it against Talos https://www.talos.dev/ but their lack of support for a persistent storage partition (only separate storage device) really hurts most small home / office usage I'd want to try.

What are the advantages of your project over conceptually similar projects that already exist, like MicroOS (https://microos.opensuse.org/) ?

I would suggest you to check either Leap Micro or MicroOS out.

I use MicroOS (https://microos.opensuse.org/), to keep the base operating system clean you'd install helper tools for constructing containers in a container... so two levels of containers would be very helpful

Where OpenSuse is interesting, definitely, it's with the MicroOS concept of Immutable Installs + their strategy of btrfs snapshots - this looks absolutely great from a stability standpoint ; there are other possible strategies out there, but these people are building a truly unbreakable distro and that's fantastic.

I'm currently running/testing openSUSE's new MicroOS which is really nice but still needs some work

Hi! I just wanted to drop by ansible-libvirt-microos ; since I'm using MicroOS already on a personal server, I decided to make better usage of it, by converting it into a VM host, and setting up another VM inside so that I can deploy more vms with extra steps containers via k3s.

I myself use Fedora Silverblue with a https://ublue.it/ -based custom image, and I use home-manager for shell configuration. Sure, my GNOME layout isn't declarative, but basically everything else is. Pair that with one of the best NVIDIA driver experiences and the strong feeling of stability, it's better than most other Linuxes rn.

Take a look at ublue.it

This is a fundamental misunderstanding of immutable systems. You still have full control over what’s on your computer, you just don’t exercise that control by making irreversible changes to your core system while it’s running. You can use e.g. rpm-ostree, or even better, build a custom image with exactly the changes you want that updates and ships directly to your computer whenever you want it to.

Have you considered the Sericea(Sway) immutable Fedora spin at ublue.it?

Have you considered the nvidia images at ublue.it? They make silverblue and nvidia easy.

Try the ublue images, they have one for deepin. It’s a variant on fedoras immutable silverblue image, you could either use their iso on http://ublue.it or install silverblue and rebase to the deepin image via:

ublue.it

This is indeed a blind spot. Thanks for pointing that out! Silverblue -to my knowledge- doesn't do a lot to address this. Though, 3rd-party tools like Home Manager and the suite of applications developed by the folks over at uBlue might be able to limit this to a minimum. Though I'm not sure if it surpasses NixOS in this regard; for the uninitiated. Though, to my knowledge, this requires special attention and depends on the specifics of the NixOS system in question.

This hasn't been for nought as even openSUSE's Aeon (and all their immutable offerings) ship Distrobox instead. Vanilla OS also ships Distrobox instead of Toolbx. Heck, even the folks over on uBlue\1]) always mention Toolbx with Distrobox and vice versa. And it wouldn't surprise me if most of them prefer to use Distrobox instead.