In order for an application equipped with List & Label to be used for reporting (printing and exporting) within a Docker Container, certain requirements must currently be met for the host and the container so that List & Label can successfully access the printer driver. The most important steps are listed below.
The operating system for both the host and the container must be at least Windows 10 version 1809 or Windows Server 2019. Host and container should always have the same build version. In previous builds there were problems activating the print spooler within the container. Corresponding base container images from Microsoft can be found here: Docker Hub: Windows base OS images.
The container must then be started with a so-called
docker run -d -t --isolation process --name mycontainer myimage
Because of the common kernel nature of process-isolated containers, only a single instance of the printer spooler service can run on the host and all containers running there. Therefore, you must first stop the service on the host before you can start and use it in the container.
Theoretically, this requirement could be avoided by starting the container with Hyper-V isolation. Under these circumstances, however, List & Label is not able to access the printer (Microsoft XPS Document Writer) correctly. This seems to be a general problem in the Windows Docker environment, which is discussed in Issue: Windows Container - spooler service crashes without warning.
The Windows Docker world is a very dynamic environment. If the processes can be simplified or if there are new solutions in the Windows environment for Docker, we will be happy to update this information here.