Install containerized Uyuni Proxy

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

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
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

1. 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.