Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to add printer in web interface #1

Open
jeffbrl opened this issue Aug 18, 2014 · 3 comments
Open

Unable to add printer in web interface #1

jeffbrl opened this issue Aug 18, 2014 · 3 comments

Comments

@jeffbrl
Copy link

jeffbrl commented Aug 18, 2014

I am running Docker version 1.1.2. When I try to add a printer, I get a "Add Printer Error", "Broken pipe" error.

E [18/Aug/2014:16:24:45 +0000] Unable to communicate with avahi-daemon: Daemon not running
E [18/Aug/2014:16:30:00 +0000] [CGI] CUPS-Get-Devices request failed with status 500: Broken pipe
E [18/Aug/2014:16:30:28 +0000] Unable to communicate with avahi-daemon: Daemon not running
E [18/Aug/2014:16:34:47 +0000] [CGI] CUPS-Get-Devices request failed with status 500: Broken pipe

I don't see avahi being installed in the Dockerfile.

@ticosax
Copy link
Owner

ticosax commented Aug 18, 2014

Yes Avahi is not running within this container.

The main reason is that I couldn't mount the dbus socket within the container.
Maybe with recent versions of docker it is now possible.
I didn't tried recently, because I do not need auto-discovery for my use-case.
You can try, if it works, the best I think is to run avahi in its own container then link avahi to cups container.
Then I'm willling to extend configuration of CUPS to reach avahi from its new location.
Assuming it is possible.

@jeffbrl
Copy link
Author

jeffbrl commented Aug 18, 2014

I did notice a dbus error when docker builds the image.

  • exec /usr/sbin/cupsd -f
    process 1: arguments to dbus_connection_unref() were incorrect, assertion "connection != NULL" failed in file ../../dbus/dbus-connection.c line 2794.
    This is normally a bug in some application using the D-Bus library.

I can get by without auto-discovery. Thanks for writing this software, ticosax.

@ticosax
Copy link
Owner

ticosax commented Aug 18, 2014

Last time I tried was in January 2014.
It means there is a chance it works now, since docker evolved a lot since.
Just give it a try, unfortunately I can't do it at the moment.

Autodiscovery might be a useful feature to have.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants