The space is probably required for btrfs snapshots and to keep the last "good" image around in case a rollback is needed.

You're most probably right. I run my system on a 20gb btrfs partition and I have run into issues before where I ran out of space because of one big binary file that was in every snapshot.

That shouldn't be an issue. Btrfs snapshots are copy-on-write, so unless all blocks changed the big binary file should be there just once.

Yeah.. It happened to be a qcow2 image for a virtual machine. I meant to put it on another disk but accidentally forgot to set the right path.

Well..that's been addressed now: https://kubic.opensuse.org/blog/2020-11-23-requirements/

That is what I was thinking, a very heavy "micro" instance.

I am curious what exactly this is envisioned for. Running micro services do not require such things and the system requirements are so heavy, it would need more hardware to run that just running them all in a normal distro.

I never jumped on the container bandwagon since it seems like it adds overhead for very little gain that can't be done with much lighter solution.

JeOS is the SUSE OS for small footprint virtualized environments.

I'm not too sure what niche MicroOS is supposed to fill that JeOS and the full-weight Leap don't already cover.

MicroOS just seems to be answer to RedHat's Silverblue, but with no clear use case in the SUSE/openSUSE product lineup. It makes some sense as a tech demo for an immutable OS, but not much sense as an operational product.

JeOS it's a striped down version of a full blown linux bistro. Think Like RH,Centos. Can be used as a VM os or for anything else.

MicroOS it's a cloud OS linux, more like: CoreOS, RancherOS, AtomicOS. I think it's a default choose for Kubernetes environments.

I've been using JeOS for k8s hosts of Rancher environments since RancherOS was deprecated and I'm glad that they finally released a cloud OS like MicroOS. In case of k8s upgrades, rollbacks and upgrades need to me minimised as much as possible. This OS allow to have all of that in a breeze since it's all based on static images.

JeOS is just a minimal installation into a VM harddisk, that's where the differences end. So it's actually more of a different installation/deployment method than a different distro.

So it's for Kubernetes nodes, VMs and bare metal?

yup