I had a reasonably good time with it. I had issues with btrfs, which is why I moved off it and went to Fedora IoT for pretty much the same benefits.

For me, btrfs caused multiple drive corruptions because of unexpected power offs, and I didn’t feel like trying to fix that on the fly - it might have been drives that were incompatible with CoW because of firmware “optimisations” that break if a write isn’t completed prior to power off.

In general, outside of that, it was pretty solid. I didn’t find much use for the orchestration/setup tooling they include, and I found their documentation pretty sporadic unfortunately. Fedora IoT has the advantage of basically being silverblue, with rpm-ostree, so it’s easy to find people using it and discussing it.

Host system doesn’t matter. Unless you are familiar with zypper and prefer how things work in SUSE, you are not going to be getting any benefits using MicroOS.

I used aeon on my most recent build and can’t wait to use it again.

Micro os is best when doing one thing. I’m using aeon to run containers.

I was drawn to microOS because I am a shit sys admin. MicroOS updates nightly, snapshots itself and now that I have my core services set I don’t need to touch it. What is not to enjoy about that?