Air-Gapped Installation of Uyuni Proxy

[killproc84]

Hi,
My idea for the Uyuni proxy was to have a Uyuni server up front that gets internet access, retrieves the packages, and supplies the servers, which are located in a secure environment, via the Uyuni proxy. I did a POC two years ago, back then with RPM packages that came via the Uyuni server, and it worked great. Now I can finally set up the environment. Now i have to do it with the containers, and any instructions require internet access at the proxy for mgrpxy, or better, podman, which then wants to reach regristry.opensuse.org. I've now tried pulling the proxy images via the Uyuni server, distributed them to the proxy host, and could now start them – but how do I then get the configuration created on the Uyuni server into it? I can pass it with mgrpxy, but it doesn't seem to accept the local container images, right?
Why isn't there documentation for the Uyuni proxy, which isn't allowed to access the internet? Isn't that the whole idea behind the proxy? There's also air-gapped documentation for the server, but that makes less sense than for the proxy....

Thank you.
Regards,
Killproc

[rjmateus]

We are preparing rpm's packages that will have the container images.
In the meantime you the approach you describe, and mgrpxy should be able to use the local images.
Documentation needs to be improved