Image Building and Management

1. Image Building Overview

Uyuni enables system administrators to build containers and OS Images and push the results to an image store.

Procedure: Building and Pushing Images

Define an image store.
Define an image profile and associate it with a source (either a git repository or a directory).
Build the image.
Push the image to the image store.

Uyuni supports these two build types: Dockerfile and the Kiwi build type. The Kiwi build type is used to build system, virtual, and other images.

The image store for the Kiwi build type is pre-defined as a file system directory at /srv/www/os-images on the server. Uyuni serves the image store over HTTPS from https://<SERVER-FQDN>/os-images/. The image store location is unique and is not customizable.

Images are stored in /srv/www/os-image/ORGANIZATION-ID.

2. Container Images

2.1. Requirements

The containers feature is available for Salt clients running SUSE Linux Enterprise Server 12 or later. Before you begin, ensure your environment meets these requirements:

A published git repository containing a Dockerfile and configuration scripts. The repository can be public or private, and should be hosted on GitHub, GitLab, or BitBucket.
A properly configured image store, such as a Docker registry.

For more information on containers, see https://documentation.suse.com/container/all/html/Container-guide/.

2.2. Create a Build Host

To build images with Uyuni, you need to create and configure a build host. Container build hosts are Salt clients running SUSE Linux Enterprise 12 or later. This section guides you through the initial configuration for a build host.

The operating system on the build host must match the operating system on the targeted image.

For example, build SUSE Linux Enterprise Server 15 based images on a build host running SUSE Linux Enterprise Server 15 (SP2 or later) OS version. Build SUSE Linux Enterprise Server 12 based images on a build host running SUSE Linux Enterprise Server 12 SP5 or SUSE Linux Enterprise Server 12 SP4 OS version.

Cross-architecture builds are not supported.

From the Uyuni Web UI, perform these steps to configure a build host:

Procedure: Building a Host

Select a Salt client to be designated as a build host from the Systems Systems overview page.
From the System Details page of the selected client assign the containers modules. Navigate to Software Software Channels and enable the containers module (for example, SLE-Module-Containers15-Pool and SLE-Module-Containers15-Updates). Continue with Next.
Schedule the Software Channel Change, and click Confirm.
From the System Details tab select Properties page, and enable Container Build Host from the Add-on System Types list. Confirm by clicking Update Properties.
Install all required packages by applying Highstate. From the system details tab select States Highstate, and click Apply Highstate. Alternatively, apply Highstate from the Uyuni Server command line:
```
salt '$your_client' state.highstate
```

2.3. Create an Activation Key for Containers

The containers built with Uyuni use channels associated to the activation key as repositories when building the image. This section guides you through creating an ad-hoc activation key for this purpose.

To build a container, you need an activation key that is associated with a channel other than SUSE Manager Default.

Procedure: Creating an Activation Key

Select Systems Activation Keys.
Click Create Key.
Enter a Description and a Key name. Use the drop-down menu to select the Base Channel to associate with this key.
Confirm with Create Activation Key.

For more information, see Activation Keys.

2.4. Create an Image Store

All built images are pushed to an image store. This section contains information about creating an image store.

Procedure: Creating Image Store

Select Images Stores.
Click Create to create a new store.
Define a name for the image store in the Label field.
Provide the path to your image registry by filling in the URI field, as a fully qualified domain name (FQDN) for the container registry host (whether internal or external).
```
registry.example.com
```
The Registry URI can also be used to specify an image store on a registry that is already in use.
```
registry.example.com:5000/myregistry/myproject
```
Click Create to add the new image store.

2.5. Create an Image Profile

All container images are built using an image profile, which contains the building instructions. This section contains information about creating an image profile with the Uyuni Web UI.

Procedure: Creating an Image Profile

To create an image profile select Images Profiles and click Create.
Provide a name for the image profile by filling in the Label field.

If your container image tag is in a format such as myproject/myimage, make sure your image store registry URI contains the /myproject suffix.
Use Dockerfile as the Image Type.
Use the drop-down menu to select your registry from the Target Image Store field.

In the Path field, type a GitHub, GitLab, or BitBucket repository URL. The path can also be a local directory on the build host. The URL should be http, https, or a token authentication URL. For GitHub or GitLab, use one of these formats:

GitHub Path Options

GitHub single user project repository

https://github.com/USER/project.git#branchname:folder

GitHub organization project repository

https://github.com/ORG/project.git#branchname:folder

GitHub token authentication

If your git repository is private, modify the profile’s URL to include authentication. Use this URL format to authenticate with a GitHub token:
```
https://USER:<AUTHENTICATION_TOKEN>@github.com/USER/project.git#master:/container/
```

GitLab single user project repository

https://gitlab.example.com/USER/project.git#master:/container/

GitLab groups project repository

https://gitlab.example.com/GROUP/project.git#master:/container/

GitLab token authentication

If your git repository is private and not publicly accessible, you need to modify the profile’s git URL to include authentication. Use this URL format to authenticate with a GitLab token:

https://gitlab-ci-token:<AUTHENTICATION_TOKEN>@gitlab.example.com/USER/project.git#master:/container/

If you do not specify a git branch, the master branch is used by default. If a folder is not specified, the image sources (Dockerfile sources) are expected to be in the root directory of the GitHub or GitLab checkout.

Select an Activation Key. Activation keys ensure that images using a profile are assigned to the correct channel and packages.

When you associate an activation key with an image profile you are ensuring any image using the profile uses the correct software channel and any packages in the channel.
Click the Create button.

2.5.1. Example Dockerfile Sources

An Image Profile that can be reused is published at https://github.com/SUSE/manager-build-profiles.

The ARG parameters ensure that the built image is associated with the desired repository served by Uyuni. The ARG parameters also allow you to build image versions of SUSE Linux Enterprise Server which may differ from the version of SUSE Linux Enterprise Server used by the build host itself.

For example: The ARG repo parameter and the echo command pointing to the repository file, creates and then injects the correct path into the repository file for the desired channel version.

The repository is determined by the activation key that you assigned to your image profile.

FROM registry.example.com/sles12sp2
MAINTAINER Tux Administrator "tux@example.com"

### Begin: These lines are required for use with {productname}

ARG repo
ARG cert

# Add the correct certificate
RUN echo "$cert" > /etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT.pem

# Update certificate trust store
RUN update-ca-certificates

# Add the repository path to the image
RUN echo "$repo" > /etc/zypp/repos.d/susemanager:dockerbuild.repo

### End: These lines are required for use with {productname}

# Add the package script
ADD add_packages.sh /root/add_packages.sh

# Run the package script
RUN /root/add_packages.sh

# After building remove the repository path from image
RUN rm -f /etc/zypp/repos.d/susemanager:dockerbuild.repo

2.5.2. Using Custom Info Key-value Pairs as Docker `buildargs`

You can assign custom info key-value pairs to attach information to the image profiles. Additionally, these key-value pairs are passed to the Docker build command as buildargs.

For more information about the available custom info keys and creating additional ones, see Custom System Information.

2.6. Build an image

There are two ways to build an image. You can select Images Build from the left navigation bar, or click the build icon in the Images Profiles list.

Procedure: Building an Image

Select Images Build.
Add a different tag name if you want a version other than the default latest (only relevant to containers).
Select Build Profile and Build Host.

Notice the Profile Summary to the right of the build fields. When you have selected a build profile, detailed information about the selected profile is displayed in this area.
To schedule a build click the Build button.

2.7. Import an Image

You can import and inspect arbitrary images. Select Images Image List from the left navigation bar. Complete the text boxes of the Import dialog. When it has processed, the imported image is listed on the Image List page.

Procedure: Importing an Image

From Images Image list click Import to open the Import Image dialog.
In the Import Image dialog complete these fields:

Image store

The registry from where the image is pulled for inspection.

Image name

The name of the image in the registry.

Image version

The version of the image in the registry.

Build host

The build host that pulls and inspects the image.

Activation key

The activation key that provides the path to the software channel that the image is inspected with.
For confirmation, click Import.

The entry for the image is created in the database, and an Inspect Image action on Uyuni is scheduled.

When it has been processed, you can find the imported image in the Image List. It has a different icon in the Build column, to indicate that the image is imported. The status icon for the imported image can also be seen on the Overview tab for the image.

2.8. Troubleshooting

These are some known problems when working with images:

HTTPS certificates to access the registry or the git repositories should be deployed to the client by a custom state file.
SSH git access using Docker is currently unsupported.

3. OS Images

OS Images are built by the Kiwi build system. The output image is customizable and can be PXE, QCOW2, LiveCD, or other types of images.

For more information about the Kiwi build system, see the Kiwi documentation.

3.1. Requirements

The Kiwi image building feature is available for Salt clients running SUSE Linux Enterprise Server 12 and SUSE Linux Enterprise Server 11.

Kiwi image configuration files and configuration scripts must be accessible in one of these locations:

Git repository
HTTP or HTTPS hosted tar archive
Local directory on the build host

For an example of a complete Kiwi repository served by git, see https://github.com/SUSE/manager-build-profiles/tree/master/OSImage.

You need at least 1 GB of RAM available for hosts running OS Images built with Kiwi. Disk space depends on the actual size of the image. For more information, see the documentation of the underlying system.

3.2. Create a Build Host

To build all kinds of images with Uyuni, create and configure a build host. OS Image build hosts are Salt clients running on SUSE Linux Enterprise Server 15 (SP2 or later) or SUSE Linux Enterprise Server 12 (SP4 or later).

This procedure guides you through the initial configuration for a build host.

The operating system on the build host must match the operating system on the targeted image.

Cross-architecture builds are not possible. For example, you must build Raspberry PI SUSE Linux Enterprise Server 15 SP3 image on a Raspberry PI (aarch64 architecture) build host running SUSE Linux Enterprise Server 15 SP3.

Procedure: Configure the Build Host in the Uyuni Web UI

Select a client to be designated as a build host from the Systems Overview page.
Navigate to the System Details Properties tab, enable the Add-on System Type OS Image Build Host. Confirm with Update Properties.
Navigate to System Details Software Software Channels, and enable the required software channels depending on the build host version.
- SUSE Linux Enterprise Server 12 build hosts require Uyuni Client tools (SLE-Manager-Tools12-Pool and SLE-Manager-Tools12-Updates).
- SUSE Linux Enterprise Server 15 build hosts require SUSE Linux Enterprise Server modules SLE-Module-DevTools15-SP4-Pool and SLE-Module-DevTools15-SP4-Updates.
- Schedule and click Confirm.
Install Kiwi and all required packages by applying Highstate. From the system details page select States Highstate and click Apply Highstate. Alternatively, apply Highstate from the Uyuni Server command line:
```
salt '$your_client' state.highstate
```

3.2.1. Uyuni Web Server Public Certificate RPM

Build host provisioning copies the Uyuni certificate RPM to the build host. This certificate is used for accessing repositories provided by Uyuni.

The certificate is packaged in RPM by the mgr-package-rpm-certificate-osimage package script. The package script is called automatically during a new Uyuni installation.

When you upgrade the spacewalk-certs-tools package, the upgrade scenario calls the package script using the default values. However if the certificate path was changed or unavailable, call the package script manually using --ca-cert-full-path <path_to_certificate> after the upgrade procedure has finished.

3.2.2. Package Script Call Example

/usr/sbin/mgr-package-rpm-certificate-osimage --ca-cert-full-path /root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT

The RPM package with the certificate is stored in a salt-accessible directory such as:

/usr/share/susemanager/salt/images/rhn-org-trusted-ssl-cert-osimage-1.0-1.noarch.rpm

The RPM package with the certificate is provided in the local build host repository:

/var/lib/Kiwi/repo

Specify the RPM package with the Uyuni SSL certificate in the build source, and make sure your Kiwi configuration contains rhn-org-trusted-ssl-cert-osimage as a required package in the bootstrap section.

Listing 1. config.xml

...
  <packages type="bootstrap">
    ...
    <package name="rhn-org-trusted-ssl-cert-osimage" bootinclude="true"/>
  </packages>
...

3.3. Create an Activation Key for OS Images

Create an activation key associated with the channel that your OS Images can use as repositories when building the image.

Activation keys are mandatory for OS Image building.

To build OS Images, you need an activation key that is associated with a channel other than SUSE Manager Default.

Procedure: Creating an Activation Key

In the Web UI, select Systems Activation Keys.
Click Create Key.
Enter a Description, a Key name, and use the drop-down box to select a Base Channel to associate with the key.
Confirm with Create Activation Key.

For more information, see Activation Keys.

3.4. Create an Image Store

OS Images can require a significant amount of storage space. Therefore, we recommended that the OS Image store is located on a partition of its own or on a Btrfs subvolume, separate from the root partition. By default, the image store is located at /srv/www/os-images.

Image stores for Kiwi build type, used to build system, virtual, and other images, are not supported yet.

Images are always stored in /srv/www/os-images/ORGANIZATION-ID and are accessible via HTTP/HTTPS https://<uyuni_host>/os-images/ORGANIZATION-ID.

3.5. Create an Image Profile

Manage image profiles using the Web UI.

Procedure: Creating an Image Profile

To create an image profile select from Images Profiles and click Create.
In the Label field, provide a name for the Image Profile.
Use Kiwi as the Image Type.
Image store is automatically selected.
Enter a Config URL to the directory containing the Kiwi configuration files. For example, a git URI such as https://github.com/SUSE/manager-build-profiles#master:OSImage/SLE-Micro54. Other options are a HTTP or HTTPS hosted tar archive or a local directory on the build host. For more information, see source format options at the end of this section.
Enter Kiwi options if needed. If the Kiwi configuration files specify multiple profiles, use --profile <name> to select the active one. For other options, see Kiwi documentation.
Select an Activation Key. Activation keys ensure that images using a profile are assigned to the correct channel and packages.

Associate an activation key with an image profile to ensure the image profile uses the correct software channel, and any packages.
Confirm with the Create button.

Source Format Options

git/HTTP(S) URL to the repository

URL to a public or private git repository containing the sources of the image to be built. Depending on the layout of the repository the URL can be:
```
https://github.com/SUSE/manager-build-profiles
```
You can specify a branch after the # character in the URL. In this example, we use the master branch:
```
https://github.com/SUSE/manager-build-profiles#master
```
You can specify a directory that contains the image sources after the : character. In this example, we use OSImage/POS_Image-JeOS6:
```
https://github.com/SUSE/manager-build-profiles#master:OSImage/POS_Image-JeOS6
```
HTTP(S) URL to the tar archive

URL to the tar archive, compressed or uncompressed, hosted on the webserver.
```
https://myimagesourceserver.example.org/MyKiwiImage.tar.gz
```
Path to the directory on the build host

Enter the path to the directory with the Kiwi build system sources. This directory must be present on the selected build host.
```
/var/lib/Kiwi/MyKiwiImage
```

3.5.1. Example of Kiwi Sources

Kiwi sources consist at least of config.xml. Usually, config.sh and images.sh are present as well. Sources can also contain files to be installed in the final image under the root subdirectory.

For information about the Kiwi build system, see the Kiwi documentation.

SUSE provides examples of fully functional image sources at the SUSE/manager-build-profiles public GitHub repository.

Listing 2. Example of JeOS config.xml

<?xml version="1.0" encoding="utf-8"?>

<image schemaversion="6.1" name="POS_Image_JeOS6">
    <description type="system">
        <author>Admin User</author>
        <contact>noemail@example.com</contact>
        <specification>SUSE Linux Enterprise 12 SP3 JeOS</specification>
    </description>
    <preferences>
        <version>6.0.0</version>
        <packagemanager>zypper</packagemanager>
        <bootsplash-theme>SLE</bootsplash-theme>
        <bootloader-theme>SLE</bootloader-theme>

        <locale>en_US</locale>
        <keytable>us.map.gz</keytable>
        <timezone>Europe/Berlin</timezone>
        <hwclock>utc</hwclock>

        <rpm-excludedocs>true</rpm-excludedocs>
        <type boot="saltboot/suse-SLES12" bootloader="grub2" checkprebuilt="true" compressed="false" filesystem="ext3" fsmountoptions="acl" fsnocheck="true" image="pxe" kernelcmdline="quiet"></type>
    </preferences>
    <!--    CUSTOM REPOSITORY
    <repository type="rpm-dir">
      <source path="this://repo"/>
    </repository>
    -->
    <packages type="image">
        <package name="patterns-sles-Minimal"/>
        <package name="aaa_base-extras"/> <!-- wouldn't be SUSE without that ;-) -->
        <package name="kernel-default"/>
        <package name="salt-minion"/>
        ...
    </packages>
    <packages type="bootstrap">
        ...
        <package name="sles-release"/>
        <!-- this certificate package is required to access {productname} repositories
             and is provided by {productname} automatically -->
        <package name="rhn-org-trusted-ssl-cert-osimage" bootinclude="true"/>

    </packages>
    <packages type="delete">
        <package name="mtools"/>
        <package name="initviocons"/>
        ...
    </packages>
</image>

3.6. Build an Image

There are two ways to build an image using the Web UI. Either select Images Build, or click the build icon in the Images Profiles list.

Procedure: Building an Image

Select Images Build.
Add a different tag name if you want a version other than the default latest (applies only to containers).
Select the Image Profile and a Build Host.

A Profile Summary is displayed to the right of the build fields. When you have selected a build profile, detailed information about the selected profile is shown here.
To schedule a build, click the Build button.

The build server cannot run any form of automounter during the image building process. If applicable, ensure that you do not have your Gnome session running as root. If an automounter is running, the image build finishes successfully, but the checksum of the image is different and causes a failure.

After the image is successfully built, the inspection phase begins. During the inspection phase SUSE Manager collects information about the image:

List of packages installed in the image
Checksum of the image
Image type and other image details

If the built image type is PXE, a Salt pillar is also generated. Image pillars are stored in the database and the Salt subsystem can access details about the generated image. Details include where the image files are located and provided, image checksums, information needed for network boot, and more.

The generated pillar is available to all connected clients.

3.7. Troubleshooting

Building an image requires several dependent steps. When the build fails, investigating Salt states results and build log can help identify the source of the failure. You can carry out these checks when the build fails:

The build host can access the build sources
There is enough disk space for the image on both the build host and the Uyuni server
The activation key has the correct channels associated with it
The build sources used are valid
The RPM package with the Uyuni public certificate is up to date and available at /usr/share/susemanager/salt/images/rhn-org-trusted-ssl-cert-osimage-1.0-1.noarch.rpm. For more on how to refresh a public certificate RPM, see Create a Build Host.

3.8. Limitations

The section contains some known issues when working with images.

HTTPS certificates used to access the HTTP sources or git repositories should be deployed to the client by a custom state file, or configured manually.
Importing Kiwi-based images is not supported.

4. List of Built Images

To list available built images select Images Image List. A list of all images is displayed.

Displayed data about images includes an image Name, its Version, Revision, and the build Status. You can also see the image update status with a listing of possible patch and package updates that are available for the image.

For OS Images, the Name and Version fields originate from Kiwi sources and are updated at the end of successful build. During building or after failed build these fields show a temporary name based on profile name.

Revision is automatically increased after each successful build. For OS Images, multiple revisions can co-exist in the store.

For Container Images the store holds only the latest revision. Information about previous revisions (packages, patches, etc.) are preserved and it is possible to list them with the Show obsolete checkbox.

Clicking the Details button on an image provides a detailed view. The detailed view includes an exact list of relevant patches, list of all packages installed within the image and a build log.

Clicking the Delete button deletes the image from the list. It also deletes the associated pillar, files from OS Image Store and obsolete revisions.

The patch and the package list is only available if the inspect state after a build was successful.