Skip to content

Container Images

Status

Implemented. CI builds all images below. All images run on the E2E cluster.

The upstream Foreman images are based on CentOS Stream 10, declare named users, and have no permissions for random UIDs. This project builds its own images on UBI 9, from images/<name>/Containerfile.

Image Base Content Platforms
ghcr.io/slauger/foreman-operator UBI 9 minimal Operator binary amd64, arm64
ghcr.io/slauger/foreman-operator-foreman UBI 9, boot disk tools from CentOS Stream 9 Foreman 5.0 RPMs, VMware support, and the plugin catalog amd64
ghcr.io/slauger/foreman-operator-smart-proxy UBI 9 foreman-proxy, smart_proxy_dhcp_dnsmasq, smart_proxy_discovery, dnsmasq, bind-utils, the dnsmasq supervisor, ipmitool, and the Dynflow, Remote Execution SSH, and Ansible plugins with the OpenSSH client and ansible-core amd64
ghcr.io/slauger/foreman-operator-boot-files UBI 9 minimal, files from CentOS Stream 9 syslinux, GRUB 2, and shim boot loaders amd64
ghcr.io/slauger/foreman-operator-frontend UBI 9 httpd, mod_ssl; runs as the container httpd in the Foreman web pods, the configuration is mounted by the operator amd64, arm64

Foreman and Smart Proxy RPMs exist for x86_64 only.

Tags

Source Tag
Push to develop develop
Push to feat/** or fix/** Branch name with slashes replaced by dashes, for example feat-smart-proxy
Weekly schedule develop
Manual run The given tag
Release The version, for example 0.1.0, and latest

The operator uses the tag of its --default-image-tag flag for every component image unless a resource sets image.tag or image.digest. The chart sets the flag to its appVersion, so a released chart runs the images of the same release. Release images are signed with cosign, see Supply Chain Security.

Versions

The Foreman and Smart Proxy Containerfiles pin every Foreman, Smart Proxy, and plugin RPM to an exact version-release, for example ARG FOREMAN_RPM=5.0.1-2.el9. Two builds of one commit install the same versions of these packages. Packages from UBI 9 and CentOS Stream 9 are not pinned; the weekly rebuild of develop picks up their errata.

Renovate tracks the pins with its rpm datasource, which reads the repository metadata under yum.theforeman.org/{releases,plugins}/<version>/el9/x86_64/repodata/:

Update Renovate PR Merge
New RPM of Foreman, Smart Proxy, or a plugin One grouped PR, Foreman RPMs By hand, after an E2E run on the test cluster
New Foreman release, from the x.y.0 tags of theforeman/foreman Foreman release, one PR per minor By hand. The PR changes only FOREMAN_VERSION; the repository URLs in the renovate: comments and all RPM pins must be updated in the same PR. Foreman upgrades one minor at a time.

Smart Proxy image

ipmitool is in the RHEL 9 AppStream but not in UBI 9. A build stage downloads the CentOS Stream 9 package and verifies its signature, and the final stage installs it. Its dependencies all come from UBI 9. rubygem-rubyipmi then installs from the Foreman repository. freeipmi is not included, because it pulls in systemd.

foreman-proxy also hard-requires rubygem-ruby-libvirt, which needs libvirt-libs and is not in the UBI repositories. The image therefore installs all other dependencies from the repositories and then installs foreman-proxy, rubygem-smart_proxy_dhcp_dnsmasq, and rubygem-smart_proxy_discovery with rpm --nodeps. The build fails if any other dependency is unsatisfied. The libvirt providers cannot be used.

The Foreman plugins repository is unsigned upstream (gpgcheck=0), so only the digests of the plugin RPMs are verified. bind-utils provides nsupdate for the DNS feature.

The same image runs both containers of the proxy pod: the Smart Proxy as an unprivileged user, and dnsmasq through dnsmasq-supervisor, see Provisioning.

Boot files image

The boot loaders come from CentOS Stream 9 packages (syslinux-tftpboot, grub2-efi-x64, shim-x64), because they are not in UBI 9. The image only contains static files: syslinux in the root, and GRUB 2 and shim under grub2/. Its default command copies them into /var/lib/tftpboot. The image has no RPM database, so /usr/share/licenses/foreman-boot-files/PACKAGES names each package with its source RPM, next to the GRUB 2 license text. syslinux-tftpboot and shim-x64 ship no license file. License: GPL-2.0-or-later AND GPL-3.0-or-later AND BSD-2-Clause-Patent.

Package availability

Checked against UBI 9 BaseOS, AppStream, and CodeReady Builder, plus the Foreman 5.0 EL9 repositories, from repository metadata on 2026-11-10.

Package set Result
foreman, foreman-service, foreman-postgresql, foreman-redis, foreman-dynflow-sidekiq Installed in the Foreman image
The plugins of the catalog, foreman-vmware Installed
foreman-proxy Installed with --nodeps, without rubygem-ruby-libvirt
ipmitool Not in UBI 9, installed from CentOS Stream 9
foreman-bootloaders-redhat GRUB and shim packages are missing, replaced by the boot-files image
foreman_bootdisk Installed; its tools come from CentOS Stream 9, see Plugins
dnsmasq, httpd, mod_ssl, bind-utils In UBI 9
dhcp-server, tftp-server, kea, freeipmi Not in UBI 9

UBI 10 has not been checked.

Random UID support

Images follow the usual pattern: a numeric USER 1001:0, group 0 owning writable paths with chmod -R g=u, and HOME set explicitly. The operator runs every container with a read-only root filesystem, so anything the images write at runtime must go to a mounted volume. The Foreman image removes the secrets generated by the RPM scriptlets and reads ENCRYPTION_KEY and SECRET_KEY_BASE from the environment.

Licensing

The images contain GPL-licensed software, including Foreman and Smart Proxy. Containerfiles in this repository are Apache-2.0. Each image carries an org.opencontainers.image.licenses label. RPMs are installed unpatched, and their license texts stay in /usr/share/licenses. The SBOMs attached to every release list each package with its source RPM. The release notes name where the distributors publish the matching sources: the Foreman and plugin repositories under yum.theforeman.org/{releases,plugins}/<version>/el9/source/, the UBI 9 source repositories, and CentOS Stream 9 for ipmitool and the boot loaders. The project does not host a copy of the sources yet.