This wiki was updated to MediaWiki 1.37. If you notice any issues, please report them to admin[at]


Jump to: navigation, search


Find the best way in which ALP can be deployed to bare-metal system in those cases in which a simple "copy a pre-built image into the device" is not enough.
Cover the use-case of current SLE and openSUSE users with complex needs regarding hardware that cannot be configured easily after the initial installation (eg. network-based storage, non-automatic network setup, etc.).
Provide a mechanism that is useful for interactive and for unattended installations and also for both local and remote ones.

Current members


A full-feature installer as previously available on SLE 15 or openSUSE Leap is not expected in ALP. The goal is to deploy the Host OS and leave the rest of the system configuration to the configuration management.

See more considerations at openSUSE:ALP/Workgroups/Installation/Context

Current status

Updated: 2022-06-23

The work group is currently exploring two ideas. We are using temporary codenames for describing them.

  • Iguana: An installer that builds and deploy a customized image and that is executed as a set of containers on top of a minimal initrd.
  • D-Installer: An installer that uses YaST components under the hood and offers a web-based interface.

Both projects could actually be complementary, since both promote the idea of small interchangeable components.

  • Current status of Iguana. See
    • At early research phase: currently an initrd with Podman (Podman to be removed/streamlined in the future)
    • The plan is to develop a mechanism inspired by GitHub Actions to somehow define how containers should be executed and should communicate on top of that initrd. Not started yet.
  • Current status of D-Installer. See
    • Created a CLI that can be used to control the process or to implement unattended installation (video).
    • Added support to install Leap Micro
    • WIP: split into several services that work in parallel as different processes


ALP will be a very image-oriented distribution. Even the installer is expected to base its work in images (by any of the mechanisms described above) but:

  • We do not know what the image building tooling will look like at this point.
  • We do not know how the images produced by this tooling will look like

Regular meetings

Every other Monday at 10am UTC at


Tasks tracking