Bug 46854 – Add the docker network to the allowed network for the printer service

Bug 46854 - Add the docker network to the allowed network for the printer service


Summary:	Add the docker network to the allowed network for the printer service

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Printserver
Version:	UCS 4.3
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-04-19 15:24 CEST by Nico Gulden
Modified:	2021-05-14 16:34 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.046
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:	Yes
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2018041921000411
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Nico Gulden

2018-04-19 15:24:17 CEST

Currently it is not possible to access the print service from inside a docker container of an app. This functionality is needed for a potential app.

By default only the network of the print service's host has access to it. The default configuration should also include the docker network. The docker image though would need a cups-client installed and configured.

> ucr set cups/location/base='10.200.7.0/255.255.255.0 172.17.0.0/255.255.0.0'

-> service cups restart

@container-> more /etc/cups/client.conf
ServerName 172.17.42.1 # -> ip of the Docker Bridge of the host

@container-> lpstat -a
printer1 accepting requests since Thu 19 Apr 2018 01:47:18 PM CEST


See Ticket#2018041921000411 for details.

Comment 1 Alec Clews 2018-04-20 01:13:30 CEST

I am from the vendor for this feature request.

After some more reflection I don't think this approach will address our requirement.

PaperCut monitors and controls print jobs by adding a new CUPS backend on the CUPS server. So we actually need to run on the CUPS server.

I think, that for MVP, it will be more effective to install a CUPS server in the PaperCut image. This will be used instead of the UCS print server

We can think about this again once we get more feedback.

Seem reasonable? I know very little about the Univention product so I could be completely wrong.

Comment 2 Ingo Steuwer

2021-05-14 15:41:55 CEST

This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.