OpenPrinting / OpenPrinting/ghostscript-printer-app
Docker container should be able to interact with host avahi-daemon
Nobody has claimed this yet.
- Dominant language
- PostScript
- Stars
- 44
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
On systems like TrueNAS, it is not possible to disable the host's avahi-daemon, and it takes over the 5353 port on every interface. Which means that the docker container cannot expose printers to the network.
Currently, attempting to bind-mount /var/run/dbus to the docker container in an attempt to make it use the system avahi-daemon makes the host very unhappy because the container's dbus daemon stomps the host's file.
With CUPS, you can bind-mount /var/run/dbus to a container that runs CUPSD and it happily uses that avahi-daemon to share printers over the network.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the container configuration and startup behavior around /var/run/dbus, then compare the described CUPS bind-mount approach. Done means the container can use the host avahi-daemon to expose printers without its D-Bus daemon overwriting the host socket or requiring port 5353 to be rebound.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100