Containerized SUSE Manager Proxy Setup
Once container host for SUSE Manager Proxy containers is prepared, setup of containers require few additional steps to finish configuration.
-
Generate SUSE Manager Proxy configuration archive file
-
Transfer configuration archive to the container host prepared in installation step and extract it
-
Start
systemd
proxy services
1. Create and generate SUSE Manager Proxy configuration
Configuration of SUSE Manager Proxy is generated by SUSE Manager Server and this configuration generation is required to be done for each containerized proxy.
There are two ways how to generate SUSE Manager configuration: use web interface or spacecmd
command.
-
In the Web UI, navigate to
and fill the required data: -
In the
Proxy FQDN
field type fully qualified domain name for the proxy. -
In the
Parent FQDN
field type fully qualified domain name for the SUSE Manager Server or another SUSE Manager Proxy. -
In the
Proxy SSH port
field type SSH port on which SSH service is listening on SUSE Manager Proxy. Recommended is to keep default 8022. -
In the
Max Squid cache size [MB]
field type maximal allowed size for Squid cache. Typically this should be at most 60% of available storage for the containers. -
In the
SSL certificate
choose if new server certificate should be generated for SUSE Manager Proxy or existing should be used.Depending on the choice then provide either path to signing CA certificate to generate new certificate or path to server certificate and its key to be used as proxy certificate.
-
Click Generate to register new proxy FQDN in SUSE Manager Server and generate configuration archive with details for container host.
-
After a few moments you are presented with file to download. Save this file locally.

-
In the console run following command:
spacecmd proxy_container_config_generate_cert -- <proxy_fqdn> <oarent_fqdn> <squid_max_cache> <admin_email>
-
Answer questions presented by script, namely SUSE Manager credentials and CA password.
This will generate file
config.zip
with configuration for the SUSE Manager Proxy containers.For more information about
spacecmd
container proxy generation, see reference:spacecmd/proxy_container.adoc.
Irrespective of what method is used to generate SUSE Manager Proxy container configuration, new system entry will appear in system list. This new entry will be shown under previously entered Proxy FQDN
value and will be of Foreign
system type.
2. Transfer SUSE Manager Proxy configuration
Both spacecmd
command and web UI ways generate configuration archive. This archive needs to be made available on container host.
Transfer this generated archive to the container host and extract it to configuration directory (by default /etc/uyuni/proxy
).
3. Start SUSE Manager Proxy containers
Container can now be started by single systemctl
command:
systemctl start uyuni-proxy-pod
systemctl enable --now uyuni-proxy-pod
Check if all containers started up as expected by calling
podman ps
Five SUSE Manager Proxy containers should be present:
-
proxy-salt-broker
-
proxy-httpd
-
proxy-tftpd
-
proxy-squid
-
proxy-ssh
And should be part of proxy-pod
container pod.