Thanks @FredrikJL

This was a lifesaver for an old Canon MX870 printer! No longer supported by Canon, not a 'plug-and-play' printer for most devices, and what drivers can be found are a nuisance for anything but Windows. A few quick notes from my experience:

 

In the end I was able to add it as an lpd network printer using the included Gutenprint driver and this connection string:

lpd://[IP.Address.Here]/queue

 

Will play around a bit to see if I can get another protocol working, but getting this working is a huge improvement!

 

 

I wasn't able to use bonjour discovery via the web UI nor console's 'lpinfo --include-schemes dnssd -v' for some reason. Had to add Root to the lpadmin group to get around a permission error, but no results listed once I got around this issue.. Adding root to lpadmin:

adduser root lpadmin

 

 

Hello,

I have a canon Imageclass MF3010, there are no drivers for this built into the container. I have been able to get the printer to work by starting the container, running the install script for the printer drivers (Linux X64 ones from canons website), then selecting them in the CUPS webui. Is there a way to add these drivers to the CUPS container, or a way to automatically run this install script every time the container is started? Thanks for any help!

Update: printer stopped working after a docker image update and I had to update the driver in CUPS to get it working again (the new driver name was identical except Gutenprint 5.3.4 vs. 5.3.5). 

 

I also noticed network discovery stopped working at some point. Fortunately the printer can be manually added via IPP.. Not a universal fix as MacOS didn't like anything /after/the/port and my kid's school Chromebook wants to hit the local network via external proxy, but other devices accepted it as a manually added IPP printer at [IP.of.UnraidServer]:631/printers/[CUPSprintername]. This matches the URL of the printer's config page, so opening the CUPS-Airprint WebUI from the Unraid web interface then navigating to your printer will provide the necessary IPP connection string (if your printer's config is available at http://123.456.789:631/printers/awesomeprinter, the IPP printer address is 123.456.789:631/printers/awesomeprinter).

 

Not sure what broke network discovery - could have been the docker image update, Unraid 7 (suspected), or a router update.. Looking like this will be a tough one to troubleshoot - network issues are rarely easy, and obscure protocols don't help. CUPS documentation seems to focus on connecting to network printers rather than getting network devices connected to CUPS.. Does a great job of communicating with old printers, but it seems to miss the mark on making them readily available. Kudos to the devs of this fork for trying to bridge the gap - hope to get things working smoothly some day.

 

On 3/3/2025 at 10:10 AM, zachamo said:

This was a lifesaver for an old Canon MX870 printer! No longer supported by Canon, not a 'plug-and-play' printer for most devices, and what drivers can be found are a nuisance for anything but Windows. A few quick notes from my experience:

 

In the end I was able to add it as an lpd network printer using the included Gutenprint driver and this connection string:

lpd://[IP.Address.Here]/queue

 

Will play around a bit to see if I can get another protocol working, but getting this working is a huge improvement!

 

 

I wasn't able to use bonjour discovery via the web UI nor console's 'lpinfo --include-schemes dnssd -v' for some reason. Had to add Root to the lpadmin group to get around a permission error, but no results listed once I got around this issue.. Adding root to lpadmin:

adduser root lpadmin

 

 

 

i will check what change
i notice the image was updated but did not had time yet to review

I've also updated to the latest and noticed that my printer no longer shows up on my network via Airprint. There have been two updates within the last month, I'm not sure which one has broken functionality. I'm going to try downgrading the container and I will report back

 

EDIT: Downgraded the container to 1.1.5 and everything seems to be working fine now

Edited May 14, 20251 yr by cinsun42

Thank you. In my case I needed to revert to 1.2.0. With 1.2.1 the printer is no longer shown on my iPhone. Reverted to 1.2.0 and it shows the printer again.

updated from 1.2.1 to 2.0
Printer shows up on Linux Client correctly, but when I try to print something error "cups-pki-invalid" appears.
Printing is not possible. Whats wrong?