CUPS server for a DYMO LabelWriter 450

Build Raspberry Pi images MegaLinter Release Please

Run a network-accessible CUPS queue for a USB-connected DYMO LabelWriter 450 on a Raspberry Pi. The image uses Debian's packaged printer-driver-dymo driver, automatically discovers the connected DYMO USB device, and exposes the shared queue over IPP.

Project technologies: Raspberry Pi, CUPS, Docker, Docker Compose, and DYMO

• uses the maintained Debian CUPS driver package;
• discovers the real usb://DYMO/... URI at runtime, with an optional override;
• starts one supervised CUPS process and waits until it is ready;
• retries safely if the USB printer is plugged in later;
• shares the queue as dymo over IPP;
• advertises the shared queue over Bonjour using the Pi's Avahi daemon; and
• never submits a print job by itself.

Network clients send print jobs over IPP to the CUPS container on the Raspberry Pi. The Pi passes the processed jobs to the USB-connected LabelWriter 450.

Architecture: network clients connect to CUPS on a Raspberry Pi, which connects to the DYMO printer over USB

• A Raspberry Pi connected to the LabelWriter 450 by USB.
• A container runtime that supports the Pi.
• Docker Compose v2 (docker compose) on the Raspberry Pi.
• The Pi's system D-Bus and Avahi services. Raspberry Pi OS normally provides both; a working <pi-hostname>.local address confirms Avahi is active.

The same Dockerfile builds for these Raspberry Pi systems:

Pi 4 and Pi 5 use the same 64-bit image variant. Docker selects the matching variant automatically when the variants are published as one multi-platform image.

git clone https://github.com/ScottGibb/Cups-Dymo-LabelWriter450.git
cd Cups-Dymo-LabelWriter450
cp .env.example .env
docker compose up -d --build
docker compose logs --follow cups

Once the logs report Configured printer queue: dymo, check the queue:

docker compose exec cups lpstat -t

These steps run on the Mac, Linux PC, or Windows PC that sends jobs to the Pi; they do not run inside the Raspberry Pi CUPS container. Start with the client setup overview, install the model-specific DYMO LabelWriter 450 driver, and apply that platform's helper.

Do not accept AirPrint, IPP Everywhere, Microsoft IPP Class Driver, Generic PostScript, or another generic driver when you need the named DYMO stocks. The guides explain how each operating system combines its DYMO driver with the network queue without double-filtering jobs.

Macs and Linux desktops with DNS-SD support can discover the Bonjour queue as DYMO LabelWriter 450 @ <pi-hostname>. Windows can use the address directly.

Confirm the Bonjour record from macOS with:

ippfind -T 10 _ipp._tcp _ipps._tcp --ls

The CUPS web interface is available at http://<pi-hostname-or-ip>:631. The shared printer's standard IPP address is:

ipp://<pi-hostname-or-ip>:631/printers/dymo

Replace <pi-hostname-or-ip> with the hostname or reserved IP address for your Pi. The client guides store this complete deployment-specific address in an IPP_URI or IppUri variable; the scripts do not assume a site hostname.

The defaults in docker-compose.yml target a standard LabelWriter 450. Copy .env.example to .env only when you need to pin the detected USB device, rename the queue or its Bonjour description, or select another supported DYMO model.

Compose mounts the Pi's system D-Bus socket into the container so CUPS can ask the existing host Avahi daemon to publish the shared queue. It does not run a second Avahi daemon or expose a separate mDNS port from the container.

The setup script looks for the first usb://DYMO/... device reported by CUPS. When several DYMO printers are connected, set PRINTER_URI to the exact URI shown by:

docker compose exec cups lpinfo -v

The documentation index separates Raspberry Pi server tasks from client-computer setup. Use the client setup guides for drivers and local queues, or the Raspberry Pi server troubleshooting guide for hardware checks, a manual test print, and recovery steps.

GitHub Actions uses MegaLinter for shell, Dockerfile, YAML, JSON, Markdown, and workflow checks, and parses the Windows PowerShell helper for syntax errors. It creates a separate pull request when auto-formatting is needed and validates image builds for linux/arm/v5, linux/arm/v7, and linux/arm64. These cover the original Raspberry Pi Zero W, 32-bit Pi 4, and 64-bit Pi 4 and Pi 5 systems.

Dependabot checks GitHub Actions and the Docker base image every week. Release Please generates release pull requests from Conventional Commits.

GPL-3.0-or-later.