Jump to content
SUSE Linux Enterprise Micro 5.0

Release Notes

SUSE Linux Enterprise Micro is a modern operating system primarily targeted for edge computing. This document provides a high-level overview of features, capabilities, and limitations of SUSE Linux Enterprise Micro 5.0.

These release notes are updated periodically. The latest version of these release notes is always available at https://www.suse.com/releasenotes (https://www.suse.com/releasenotes). General documentation can be found at https://documentation.suse.com/sle-micro/5.0 (https://documentation.suse.com/sle-micro/5.0).

Publication Date: 2021-03-16, Version: 5.0.20210316

1 SUSE Linux Enterprise Micro

1.1 Documentation

For the most up-to-date version of the documentation for SUSE Linux Enterprise Micro 5.0, see https://documentation.suse.com/sle-micro/5.0 (https://documentation.suse.com/sle-micro/5.0).

1.2 Support and life cycle

SUSE Linux Enterprise Micro is backed by award-winning support from SUSE, an established technology leader with a proven history of delivering enterprise-quality support services.

SUSE Linux Enterprise Micro 5.0 has a 12-month life cycle. For more information, see https://www.suse.com/lifecycle (https://www.suse.com/lifecycle) and the Support Policy page at https://www.suse.com/support/policy.html (https://www.suse.com/support/policy.html).

2 About the release notes

These Release Notes are identical across all architectures, and the most recent version is always available online at https://www.suse.com/releasenotes (https://www.suse.com/releasenotes).

Entries can be listed twice, if they are important and belong to more than one section.

Release notes usually only list changes that happened between two subsequent releases. Certain important entries from the release notes of previous product versions are repeated. To make these entries easier to identify, they contain a note to that effect.

However, repeated entries are provided as a courtesy only. Therefore, if you are skipping one or more releases, check the release notes of the skipped releases as well. If you are only reading the release notes of the current release, you could miss important changes.

3 General features and fixes

Information in this section applies to all architectures supported by SUSE Linux Enterprise Micro 5.0.

3.1 Installation media

There are two types of installation media of SUSE Linux Enterprise Micro. The installer ISO allows to install via YaST or AutoYaST, with the possibility to fully customize the installation. The pre-built images contain a system image already pre-configured.

There are slight differences between these two:

  • the software selection for default installation from ISO contains fewer packages than the pre-built image

  • firewalld is installed from the ISO only if it gets enabled during installation

The images have two things in common:

  • SELinux is not enabled by default

  • firewall is not enabled by default

3.2 Cockpit

For web-based management of a single node, Cockpit web management is included. It is not enabled by default and the respective firewall port is not open if firewall is enabled.

3.3 toolbox container

SUSE Linux Enterprise Micro provides the toolbox container. However, it is not part of the media and needs to be downloaded from https://registry.suse.com (https://registry.suse.com). For that the system needs to have access to the registry.

In order to install additional software into the container, you must configure the repositories. It does not define any nor does it inherit repositories from the underlying system.

3.4 System V init scripts

SUSE Linux Enterprise Micro does not support init script of system services, which are usually located in /etc/init.d directory. Even if this directory still exists, it is empty on purpose. systemd unit files should be used instead of initscripts. To start system services or to configure their status on boot, use the systemctl command instead.

4 Installing SUSE Linux Enterprise Micro

SUSE Linux Enterprise Micro 5.0 can be installed in the following ways:

  • manual installation with YaST

  • unattended installation with AutoYaST

  • unattended installation with Yomi (technology preview)

  • deployment of pre-built images

Below find notes to individual approaches.

4.1 Manually installing with YaST

The installation workflow for manual installation is similar to SUSE Linux Enterprise Server. However, it is stripped down and configuration options are more limited. For more information, see the SUSE Linux Enterprise Server documentation.

4.2 Unattended installation with AutoYaST

The installation with AutoYaST works in a similar way as for SUSE Linux Enterprise Server. The two main differences are limited set of options that can be configured via the AutoYaST profile and complete absence of the second stage of the AutoYaST workflow. For more information, see the SUSE Linux Enterprise Micro and SUSE Linux Enterprise Server documentation.

The following example shows an AutoYaST profile:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE profile>
<profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns">
    <do_registration config:type="boolean">true</do_registration>
    <install_updates config:type="boolean">true</install_updates>
      <timeout config:type="integer">-1</timeout>
      <confirm config:type="boolean">false</confirm>
      <second_stage config:type="boolean">false</second_stage>
    <products config:type="list">
    <install_recommended config:type="boolean">true</install_recommended>
    <packages config:type="list">
    <patterns config:type="list">
  <users config:type="list">
      <encrypted config:type="boolean">false</encrypted>

AutoYaST only supports a limited set of sections compared to SUSE Linux Enterprise Server:

  • bootloader

  • configuration_management

  • fcoe-client

  • files

  • firewall

  • groups

  • general

  • host

  • iscsi-client

  • kdump

  • keyboard

  • language

  • login_settings

  • networking

  • partitioning

  • partitioning_advanced

  • report

  • runlevel / services-manager

  • scripts (pre-scripts, postpartitioning-scripts, chroot-scripts)

  • security

  • software

  • ssh_import

  • suse_register

  • timezone

  • users

  • user_defaults

Note: Explicitly disable the second stage

AutoYaST can set some options in either the first or the second stage. SUSE Linux Enterprise Micro does not include a second stage. For some settings (such as networking), you need to explicitly disable the second stage:

<second_stage config:type="boolean">false</second_stage>

The example profile above already includes this line.

Note: SELinux is necessary

The system will not boot if you do not install the SELinux pattern and keep SELinux enabled.

4.3 Unattended installation with Yomi (technology preview)

To learn how to install a system with Yomi, read the documentation of SUSE Manager. Installation with Yomi is only a technology preview.

4.4 Deploying pre-built images

SUSE Linux Enterprise Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive. SUSE Linux Enterprise Micro is also provided as images for specific hardware device with a customized software selection.

To deploy an image, first identify and download the image you need. Then decompress it and write it to a storage device:

xz -d <downloaded_image.raw.xz>
dd if=<downloaded_image.raw> of=/dev/sdX

When the image is first booted, use Ignition or Combustion for initial configuration, which includes setting the root password. Otherwise, there is no way to access the system after deployment.

Ignition or Combustion are invoked only the first time the image boots. To invoke them at a later reboot, append ignition.firstboot to the kernel command line.

Ignition configuration files should be named ignition/config.ign, and can be stored on a USB stick. A minimal Ignition configuration file could look like this:

        "passwordHash":"hash, created with, for example, `openssl passwd -6`"

More information about Ignition and Combustion, including further examples, can be found at the these links:

5 Known issues

5.1 Error on console while booting with SELinux enabled

When booting the system with SELinux enabled, the console reports:

Failed to transition into init label 'system_u:system_r:init_t:s0'

This message is harmless.

5.2 Podman and firewalld

When reloading firewalld via firewall-cmd --reload, all Podman related rules go missing. For this reason, firewalld is not enabled by default during installation. For more information, see https://github.com/containers/podman/issues/5431 (https://github.com/containers/podman/issues/5431).

5.3 Cockpit not known by firewalld

firewalld does not know the Cockpit service. As a workaround, open the port in firewalld by typing this command:

firewall-cmd --zone=public --permanent --add-port=9090/tcp

5.4 Installation via VNC

The YaST installer offers installation via VNC. However, the VNC server is only available during the installation, but not for the installed system. The installer issues a warning that the respective packages cannot be installed. This is correct, you can ignore this warning.

6 Obtaining source code

This SUSE product includes materials licensed to SUSE under the GNU General Public License (GPL). The GPL requires SUSE to provide the source code that corresponds to the GPL-licensed material. The source code is available for download at https://www.suse.com/products/server/download/ (https://www.suse.com/products/server/download/) on Medium 2. For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code. Send requests by e-mail to sle_source_request@suse.com (mailto:sle_source_request@suse.com). SUSE may charge a reasonable fee to recover distribution costs.

Print this page