@rijkr This is not about containers per se, but that is where I am testing/installing. I have a container working using docker-compose on my local system. and when I push it to my production system, the cups icon under Proxy Printers does not show… presumably because savapage can’t see the running cups service.
The cups service is actually running in the container with Savapage, because I can navigate to the CUPS admin and add the printer. Synchronize does pull it in as expected, but I can’t print to it via the web client. Again presumably because it doesn’t “see” it.
@worraps As the User Manual states: The CUPS button is shown when the browser points to “localhost”, “127.0.0.1”, a “.local” address, or to the intranet IP address of the SavaPage server, and host port matches the configured SavaPage port.
@worraps Although CUPS is part of your SavaPage container, your physical printers are not. When you deploy the container in an environment where these physical printers are not visible, their CUPS counterparts show as disconnected and will not be available for proxy printing from the web app.