Last Update: 2024-01-31

Table of Contents

Introduction

Welcome to the dedicated web page for the beta of SUSE Linux Enterprise Micro (SLE Micro), the ultra-reliable, lightweight operating system purpose built for edge computing. It leverages the enterprise hardened security and compliance components of SUSE Linux Enterprise and merges them with a modern, immutable, developer-friendly OS platform.

SUSE Linux Enterprise Micro 6.0 will build upon the momentum generated by the previous Releases. SLE Micro 6.0 is based on new code base, enhanced with select features based on customer and partner requests, as well as internal feedback. The focus is migrating to the new code base ensuring a smooth migration for existing customers.  

Notable Changes

  • Rebase to the SUSE Adaptable Linux Platform
  • Support for Full Disk Encryption
  • Support for Active Directory Integration - still in development
  • Addition of cloud-init for public cloud and hypervisor images
  • SLE Micro 6.0 is based on a new codebase so please check out the Release Notes for more details about the changes
  • Refresh of other components

Planned Releases

Our plan is to release two Public Pre-Release ISOs, one Public Beta, one Public Release Candidate.   Scheduled releases:

  • Beta 2 January 30, 2024
  • First Customer ShipmentApril 2024
Important

Please note that we reserve the right to change or adapt this schedule depending on various factors. Rest assured that we will communicate if there is any change to the plan.

 

Download

SLE Micro 6.0 is available on the following architectures: aarch64, s390x and x86_64.

x86_64

aarch64

s390x

Only bootable images of SLE Micro are available for all architectures. Here is the description of each and every image:

  • Please note these are non-bootable DVD images with all packages from repo
    • SLE-Micro.aarch64-6.0-Base-SelfInstall-Beta2.install.iso
    • SLE-Micro.aarch64-6.0-Default-SelfInstall-Beta2.install.iso
    • SLE-Micro.x86_64-6.0-Base-SelfInstall-Beta2.install.iso
    • SLE-Micro.x86_64-6.0-Default-SelfInstall-Beta2.install.iso
    • SLE-Micro-6.0-Packages-aarch64-Beta2-Media1.iso
    • SLE-Micro-6.0-Packages-aarch64-Beta2-Media2.iso
    • SLE-Micro-6.0-Packages-s390x-Beta2-Media1.iso
    • SLE-Micro-6.0-Packages-s390x-Beta2-Media2.iso
    • SLE-Micro-6.0-Packages-x86_64-Beta2-Media1.iso
    • SLE-Micro-6.0-Packages-x86_64-Beta2-Media2.iso
    • SLE-Micro-6.0-Packages-aarch64-Beta2-Media1.iso
    • SLE-Micro-6.0-Packages-aarch64-Beta2-Media2.iso
    • SLE-Micro-6.0-Packages-aarch64-Beta2-Media3.iso
    • SLE-Micro-6.0-Packages-s390x-Beta2-Media1.iso
    • SLE-Micro-6.0-Packages-s390x-Beta2-Media2.iso
    • SLE-Micro-6.0-Packages-s390x-Beta2-Media3.iso
    • SLE-Micro-6.0-Packages-x86_64-Beta2-Media1.iso
    • SLE-Micro-6.0-Packages-x86_64-Beta2-Media2.iso
    • SLE-Micro-6.0-Packages-x86_64-Beta2-Media3.iso
  • Default images below are ready-to-deploy raw disk images, including podman as container engine and KVM as virtualization stack for x86_64 machines and RaspBerry Pi. During initial boot, Ignition or Combustion configuration must be provided in order to perform basic configuration (e.g. set root password).
    • SLE-Micro.aarch64-6.0-Base-Beta2.raw.xz
    • SLE-Micro.aarch64-6.0-Base-qcow-Beta2.qcow2
    • SLE-Micro.aarch64-6.0-Default-Beta2.raw.xz
    • SLE-Micro.aarch64-6.0-Default-qcow-Beta2.qcow2
    • SLE-Micro.x86_64-6.0-Base-Beta2.raw.xz
    • SLE-Micro.x86_64-6.0-Base-encrypted-Beta2.raw
    • SLE-Micro.x86_64-6.0-Base-qcow-Beta2.qcow2
    • SLE-Micro.x86_64-6.0-Base-SelfInstall-Beta2.raw.xz
    • SLE-Micro.x86_64-6.0-Base-VMware-Beta2.vmdk.xz
    • SLE-Micro.x86_64-6.0-Default-Beta2.raw.xz
    • SLE-Micro.x86_64-6.0-Default-encrypted-Beta2.raw
    • SLE-Micro.x86_64-6.0-Default-qcow-Beta2.qcow2
    • SLE-Micro.x86_64-6.0-Default-VMware-Beta2.vmdk.xz
  • Default images of SLE Micro, including podman as container engine and KVM as virtualization stack, for various types of hypervisor and storage on IBM system z.
    • SLE-Micro.s390x-6.0-Base-dasd-Beta2.raw.xz
    • SLE-Micro.s390x-6.0-Base-fba-Beta2.raw.xz
    • SLE-Micro.s390x-6.0-Base-qcow-Beta2.qcow2
    • SLE-Micro.s390x-6.0-Default-dasd-Beta2.raw.xz
    • SLE-Micro.s390x-6.0-Default-fba-Beta2.raw.xz
    • SLE-Micro.s390x-6.0-Default-qcow-Beta2.qcow2

 

Documentation

Note: The following Documents are drafts.

And will remain as such through out the SLE Micro Beta Program. Documentation for Beta Products do not yet have the quality, accuracy and content of our official documentation. However we will update these documents on the fly during the SLE Micro Beta Program.

All documentation are available at https://susedoc.github.io/:

Release Notes

  • TBD

 

Known Issues

Functional

  • bsc#1219200 - Dependency issue when installing alp_elemental_client pattern
  • bsc#1219212 - only 16M size is allocated to /boot/efi, and 'transactional-update -n

Kernel

  • bsc#1219202 - Base-RT-SelfInstall failed due to dracut-pre-mount issue (bsc#1219144)
  • bsc#1219207 - kdump doesn't work with enabled SELinux

Containers

Migration

  • bsc#1219218 - pam_systemd(login:session): Failed to release session: Interrupted system call
  • bsc#1219209 - Unable to send container stderr message to parent Broken pipe

Security

  • bsc#1217934 - openssl-3 fips install not integrated
  • bsc#1217872 - sedispatch fails with unexpected termination

Virtualization

  • bsc#1219164 - Failed to install sle-micro 6.0 guest using raw/qcow/encrypted images on sle-micro 6.0 host

Resolved Issues

  • TBD

Feedback

Whenever you find a bug or have a question while using SUSE Linux Enterprise Micro, we highly recommend that you use our mailing list first, then if it really make sense you should open a bug report.

Private Channel

In case you would like to share some sensitive data with us (data for bug reports, feedbacks, etc), please contact us at beta-programs@suse.com, and we will review your case and provide a private channel with us.

Public Mailing List

micro-beta@lists.suse.com is our dedicated Public Mailing List to discuss SUSE Linux Enterprise Beta products. It is used by the SUSE Release Team to announce new beta images and technical information, as well as for general or technical questions, feedback, or defect reports related to SUSE Linux Enterprise Beta products from our beta testers community. Only subscribers can post to our mailing lists. To subscribe, please go to http://lists.suse.com/mailman/listinfo/micro-beta. Only subscribers can post to our mailing lists. To subscribe, please go to http://lists.suse.com/mailman/listinfo/micro-beta. Please refer to our Mailing Lists Guideline for more information.  

Frequently Asked Questions

- Beta Subscription and Registration Code
Warning: Beta Registration Code

Registration is not working with your regular SLE Micro key, special Beta Registration Code is required. Thus, you don't have access to the SLE online channels/repositories and Modules without a Beta Registration Code. The Beta Registration Code is the key to unlock the Beta Subscription in our SUSE Customer Center. The Beta Subscription consist of giving access to our SLE Micro Beta Online Channels. We will not provide a beta product subscription or beta product registration code by default for the SLE Micro Beta Program. You might request one via beta-programs@suse.com, please specify if you want a registration code for which architectures.  

- Migrating from SLE Micro 5.5 to SLE Micro 6.0 Beta

Update from SLE Micro 5.5 to 6.0 is now supported. Unlike with SLES, which offers several methods, with SLE Micro there is only one method available, via transactional-update.

- Updating from SLE Micro 6.0 Beta to the next SLE Micro 6.0 Beta

Even if it's completely feasible and working, we do not recommend updating from "SLE Micro 6.0 Beta X" to "SLE Micro 6.0 Beta X+N" for your thorough beta testing. Why? Because this scenario is specific to beta and can not be compared to any SLE Micro production update scenario. During the beta phase of our products, we need the flexibility of doing important changes to packages (libraries, configuration files, features, etc), like upgrading or downgrading to different versions. Thus changes between SLE Micro Beta might look very different from regular updates we make in official SLE Micro releases. We highly recommend to test the following scenarios, whenever a new Beta version is released:  

- Updating from SLE Micro 6.0 Beta to SLE Micro 6.0 GM
Warning: Migration from Beta to Gold Master

Migrating from SLE Micro 6.0 Beta to SLE Micro 6.0 Gold Master (the final and official version) is NOT SUPPORTED. If you want to put the final version of our product in production, you need to do a fresh installation or a migration from an existing supported version. We will not support the migration from a beta product to a final release of the product. As a reminder, our SUSE Beta EULA states that you should not put SUSE Beta Products in production.    

- Contact Beta Manager

Do you have a question or an issue to report on our Beta Program? Want to get in touch with our Product Managers or Engineering team? Or simply share a feedback? Please do not hesitate to contact us via beta-programs@suse.com!