If you did not migrate your account yet, visit https://idp-portal-info.suse.com/
- Small: Lightweight images designed to be deployed for a specific use case
- Scalable: Optimized for large deployments while capable as a single machine OS
- Always up-to-date: Updates are automatically applied without impacting the running system
- Resilient: In case of trouble the system automatically rolls back to last working state
- Fast: Doesn't ship with baggage that slows it down
In other words openSUSE MicroOS is an operating system you don't have to worry about. It's designed for but not limited to container hosts and edge devices. Due to the focus on unattended operation it's especially suited for large deployments. openSUSE MicroOS inherits the openSUSE Tumbleweed and SUSE Linux Enterprise knowledge while redefining the operating system into a small, efficient and reliable distribution.openSUSE MicroOS is available as variant of openSUSE Tumbleweed or openSUSE Leap and serves as a base of openSUSE Kubic, a Container as a Service platform.
- Read-only root filesystem to avoid accidental modifications of the OS
- The Transactional Updates technology leverages btrfs snapshots to apply package updates without interfering with the running system
- health-checker to verify the OS is operational after updates. Automatically rolls back in case of trouble.
- cloud-init for initial system configuration during first boot on Cloud (includes OpenStack)
- Combustion and Ignition for initial system configuration during first boot on all other images.
- Designed to fit perfectly into existing openSUSE or SUSE Linux Enterprise environments
- Podman Container Runtime available
- Rolling Release: Every new openSUSE Tumbleweed snapshot also automatically produces a new openSUSE MicroOS release. The Leap based version automatically updates when maintenance updates for Leap are published.
The configuration file for those systems has to be created before the first boot of an image. MicroOS does not use any default password even for root, so be sure to use one Combustion, Ignition or Cloud-Init where applicable.
Based on Tumbleweed
|Platform||Base System||Container Host||First Boot Configuration|
|ISO Image||x86_64, aarch64, ppc64le||–||–|
|Raspberry Pi||armv7l, aarch64||aarch64||Combustion or Ignition|
|Pine64||aarch64||aarch64||Combustion or Ignition|
|Qemu KVM & XEN||x86_64, aarch64||x86_64, aarch64||Combustion or Ignition|
|VirtualBox||x86_64||–||Combustion or Ignition|
|VMware||x86_64 (VMX)||x86_64 (VMX)||Combustion or Ignition|
|Vagrant||x86_64, aarch64||x86_64, aarch64||Combustion or Ignition|
|Microsoft HyperV||x86_64||x86_64||Combustion or Ignition|
Based on Leap 15.2 (Experimental)
|Platform||Base System||Container Host||Realtime||First Boot Configuration|
|ISO Image||x86_64, aarch64||–||–||–|
|Raspberry Pi (3&4)||aarch64||–||–||Combustion or Ignition|
|Qemu KVM & XEN||x86_64, aarch64||x86_64, aarch64||x86_64||Combustion or Ignition|