Developers of the Opensuse leap micro ” based on the developments of the project Microos . Distribution of the Opensuse Leap Micro is positioned as a commercial version of the commercial product SUSE LINUX ENTERPRISE MICRO 5.2 What explains the unusual number of the first version – 5.2, which is selected for synchronizing the numbering of issues in both distributions. Open support time Opensuse Leap Micro 5.2 will be 4 years.
for downloads Assemblies for architectures x86_64 and ARM64 (AARMH64), supplied as with an installer (Offline-assembly, the size of 370MB), and in the form of ready-made loading images: 570MB (destined), 740MB (with Real-Time core) and 820MB. Images can be launched under the control of Xen and KVM hypervisors or on top of the equipment, including Raspberry Pi.
For configuration, you can use the instrumentation cloud-init for transmitting settings at each download or Combustion to set the settings during the first load.
The key feature of the Leap Micro is the mechanism of the atomic installation of updates, which are loaded and used automatically. Unlike atomic updates based on Ostree and SNAP used in Fedora and Ubuntu, in the Opensuse LEAP Micro, instead of constructing individual atomic images and expanding additional delivery infrastructure, a standard package manager and snapshot mechanisms in the Federal Security Service are used. To update the linux nucleus without restarting and suspension of work, Live Patchi .
The root section is mounted in mode only for reading and does not change during operation. BTRFS is used as a file system, the implementation of snapshot support in which serves as the basis for atomic switching between updates. In case of problems after applying the update, you can roll back the system to the state before installing the update. To launch insulated containers, the instrumentation with support for Runtime Podman/Cri-O and Docker.