Install containerized Uyuni Proxy

Only openSUSE Leap 15.3 and newer are supported to be used as container host for Uyuni Proxy containers.

1. Container host requirements

Table 1. Proxy Container host hardware requirements
Hardware Details Recommendation


Minimum 2 dedicated 64-bit CPU cores


Test Server

Minimum 2 GB

Production Server

Minimum 8 GB

Disk Space

Minimum 100 GB

Table 2. Proxy Container host software requirements
Software Details Remark

Connection Method


Host must be configured as a Salt client

To ensure that domain name of the Uyuni Server can be resolved by the clients: * Both container proxy and client machines must be connected to a DNS server * Reverse lookup must work

2. Install container services on the host system

Container host to be used as a base for Uyuni Proxy containers needs to be first registered as a client to the Uyuni Server.

For more information about registering client to the Uyuni Server, see Client Registration.

Uyuni Proxy containers are using podman and systemd to run and manage all proxy containers.

First step is to install the mgrpxy utility provided by the package of the same name.

The mgrpxy package is available in the container utils repository: pick the one matching the distribution in:

To install them run:

zypper in helm mgrpxy
Procedure: Installation of container utility tool mgrpxy for Uyuni Proxy
  1. Assign Containers Module software channel to the container host in the Uyuni. For more information about assigning software channels to the system, see Channel Management.

  2. Log in as root on the container host.

  3. Manually install mgrpxy package:

    zypper install mgrpxy

3. Install Uyuni Proxy containers

Uyuni Proxy containers require some volumes to be mounted for long term storage. Those volumes are automatically created by podman and can be listed using the podman volume ls command. By default, podman stores the files of the volumes in /var/lib/containers/storage/volumes. The volumes are named:

  • uyuni-proxy-squid-cache

  • uyuni-proxy-rhn-cache

  • uyuni-proxy-tftpboot

To override default volume settings, create the volumes prior to the first start of the pod using the podman volume create command.

To install the systemd service starting the Uyuni proxy, run the mgrpxy install podman /path/to/config.tar.gz command.

It is possible to add custom arguments passed to podman container pod with the one or more --podman-arg parameters to the install command.

It is possible to modify the tag to use for container images with the --tag=latest parameter to the install command.

Changing the containers images and version parameters is dangerous and can cause a non-functional system.

3.1. Using a custom container image for a service

By default, the Uyuni Proxy suite is set to use the same image version and registry path for each of its services. However, it is possible to override the default values for a specific service using the install parameters ending with -tag and -image.

For example, use it like this:

mgrpxy install podman --httpd-tag 0.1.0 --httpd-image /path/to/config.tar.gz

It adjusts the configuration file for the httpd service, where is the image to use and 0.1.0 is the version tag, before restarting it.

To reset the values to defaults, run the install command again without those parameters:

mgrpxy install podman /path/to/config.tar.gz

This command first resets the configuration of all services to the global defaults and then reloads it.

4. Allow network access for provided services on container host firewall

Uyuni Proxy containers work as so called node-port service. This means proxy container pod shares container host network TCP and UDP port space. For this reason container host firewall must be configured to accept incoming traffic on ports used by Uyuni Proxy containers. Those ports are:

  • 69/UDP - TFTP

  • 80/TCP - HTTP

  • 443/TCP - HTTPS

  • 4505/TCP - Salt

  • 4506/TCP - Salt

  • 8022/TCP - SSH

Continue with setting up the installed Uyuni Proxy as a containers at Containerized Uyuni Proxy Setup.