{"id":104086,"date":"2022-05-18T21:36:44","date_gmt":"2022-05-18T19:36:44","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/pervyj-vypusk-distributiva-opensuse-leap-micro"},"modified":"2022-05-18T21:36:44","modified_gmt":"2022-05-18T19:36:44","slug":"pervyj-vypusk-distributiva-opensuse-leap-micro","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/pervyj-vypusk-distributiva-opensuse-leap-micro","title":{"rendered":"The first release of the openSUSE Leap Micro distribution","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The developers of the openSUSE project have released the first version of the new edition of the openSUSE distribution \u2014 'Leap Micro', based on the MicroOS project. The openSUSE Leap Micro distribution is positioned as a community version of the commercial product SUSE Linux Enterprise Micro 5.2, which explains the unusual number of the first version \u2014 5.2, chosen to synchronize version numbering between both distributions. The support time for the openSUSE Leap Micro 5.2 release will be 4 years. <\/p>\n
Available for download are builds for x86_64 and ARM64 (Aarch64) architectures, provided both with an installer (Offline builds, size 370MB) and as ready-to-use boot images: 570MB (pre-configured), 740MB (with Real-Time kernel), and 820MB. The images can run under hypervisors Xen and KVM or on hardware, including Raspberry Pi boards. For configuration, the cloud-init toolkit can be used to pass settings at each boot or Combustion to set up configurations during the first boot. <\/p>\n
A key feature of Leap Micro is the atomic update installation mechanism, which downloads and applies updates automatically. Unlike the atomic updates based on ostree and snap used in Fedora and Ubuntu, openSUSE Leap Micro employs the standard package manager and filesystem snapshot mechanism instead of building separate atomic images and deploying additional delivery infrastructure. Live patches are supported for updating the Linux kernel without rebooting and halting operations. <\/p>\n
The root partition is mounted in read-only mode and does not change during operation. Btrfs is used as the filesystem, with snapshots serving as the basis for atomic switching between system states before and after updates are applied. In case of problems after updates, the system can be rolled back to a previous state. Integrated tools with runtime support for Podman\/CRI-O and Docker are provided for running isolated containers. <\/p>\n
Among the applications of Leap Micro is its use as a base system for virtualization platforms and container isolation, as well as its application in decentralized environments and microservices-based systems. Leap Micro is also an important link in forming the next generation of the SUSE Linux distribution, which plans to split the core of the distribution into two parts: a stripped-down 'host OS' for operation on hardware and a layer for application support focused on running in containers. virtual machines<\/a>. <\/p>\n