SLE 15 SP6 LTSS Base Container Image

Description

SUSE Linux Enterprise Base Container Images provide open, flexible, and secure container images. The images include container environments based on SUSE Linux Enterprise Long Term Service Pack Support (LTSS) and are available at no cost, may be freely redistributed under the BCI EULA, and are supported across a large variety of environments.

This image serves as a foundation for many SLE BCIs. It is designed to be extended for additional use cases, such as development or testing environments.

Usage

The container image includes the zypper package manager and the container-suseconnect utility. This enables access to the full SUSE Linux Enterprise Long Term Service Pack Support (LTSS) repositories with a valid subscription. The image is intended to be extended by installing packages required for your specific use case.

To build a custom image that includes the skopeo utility, use the following Containerfile:

FROM registry.suse.com/suse/ltss/sle%OS_VERSION_ID_SP%/bci-base:latest
RUN set -euo pipefail; \
    zypper -n ref; \
    zypper -n install skopeo; \
    zypper -n clean -a ; \
    rm -rf /var/log/{lastlog,tallylog,zypper.log,zypp/history,YaST2}

Then build the container using buildah:

buildah bud -t bci-skopeo .

You can also use the image interactively to create a container with skopeo installed:

$ podman run -ti --rm registry.suse.com/suse/ltss/sle%OS_VERSION_ID_SP%/bci-base:latest
# zypper -n install skopeo
...
# skopeo inspect -f "{{ .Name }}" docker://registry.suse.com/suse/ltss/sle%OS_VERSION_ID_SP%/bci-base:latest
registry.suse.com/suse/ltss/sle%OS_VERSION_ID_SP%/bci-base

Getting access to the SLE LTSS repositories

The container-suseconnect utility in the image can automatically add the full repositories into the running container if you have a valid SUSE Linux Enterprise Long Term Service Pack Support (LTSS) subscription.

Find more information about container-suseconnect in the container-suseconnect section in the container guide or in the tutorial How to use container-suseconnect.

Accessing the container image

Accessing this container image requires a valid SUSE subscription. In order to access the container image, you must login to the SUSE Registry with your credentials. There are three ways to do that which are described below. The first two methods leverage the system registration of your host system, while the third method requires you to obtain the organisation SCC mirroring credentials.

Use the system registration of your host system

If the host system you are using to build or run a container is already registered with the correct subscription required for accessing the LTSS container images, you can use the registration information from the host to log in to the registry.

The file /etc/zypp/credentials.d/SCCcredentials contains a username and a password. These credentials allow you to access any container that is available under the subscription of the respective host system. You can use these credentials to log in to SUSE Registry using the following commands (use the leading space before the echo command to avoid storing the credentials in the shell history):

set +o history
 echo PASSWORD | podman login -u USERNAME --password-stdin registry.suse.com
set -o history

Use a separate SUSE Customer Center registration code

If the host system is not registered with SUSE Customer Center, you can use a valid SUSE Customer Center registration code to log in to the registry:

set +o history
 echo SCC_REGISTRATION_CODE | podman login -u "regcode" --password-stdin registry.suse.com
set -o history

The user parameter in this case is the verbatim string regcode, and SCC_REGISTRATION_CODE is the actual registration code obtained from SUSE.

Use the organization mirroring credentials

You can also use the organization mirroring credentials to log in to the SUSE Registry:

set +o history
 echo SCC_MIRRORING_PASSWORD | podman login -u "SCC_MIRRORING_USER" --password-stdin registry.suse.com
set -o history

These credentials give you access to all subscriptions the organization owns, including those related to container images in the SUSE Registry. The credentials are highly privileged and should be preferably used for a private mirroring registry only.

Licensing

SPDX-License-Identifier: MIT

This documentation and the build recipe are licensed as MIT. The container itself contains various software components under various open source licenses listed in the associated Software Bill of Materials (SBOM).

This image is based on SUSE Linux Enterprise Server, a reliable, secure, and scalable server operating system built to power mission-critical workloads in physical and virtual environments.