Tag: Docker
Deploying Diun and Watchtower: The Decisions That Determine Whether It Actually Works
Starting point The decision to use Diun alongside Watchtower has already been made: Diun handles notification, Watchtower handles execution, and the combination restores a human checkpoint to a change surface that running :latest tags makes otherwise invisible. What that setup actually looks like, and whether it holds under real operating
Container Update Workflows: Decoupling Awareness from Action
The default is dangerous, but not for the reason you think Most containers in most homelabs run on :latest tags. The reasons are familiar: introductory Docker content defaults to it, most Compose examples don't specify versions, and pinning feels like extra work for uncertain benefit. The result is
Building the Home Assistant Docker Stack: MariaDB, Z-Wave JS UI, and the One USB Path That Survives a Reboot
The Z-Wave USB stick is invisible inside the container. Every setup guide tells you to add a devices: entry to your compose file and pass the path /dev/ttyUSB0. On first boot it works. After a reboot, the path has rotated to /dev/ttyACM0, or shifted to /dev/ttyUSB1 because
Deploying the Arr Stack: Getting Path Mapping Right Before Anything Else
The most common arr stack failure mode doesn't surface an error. Sonarr reports the download complete. NZBGet has moved the file. The import job finishes without complaint. Nothing appears in your media server. The problem is path mapping — and it was misconfigured before the first container started. This
AdGuard Home on Docker — Bridge Mode and Upstream DNS
The default AdGuard Home documentation puts it on host networking and walks you through disabling systemd-resolved to free port 53. That's one way to do it. If you're already running a layered DNS stack — an upstream resolver handling local overrides, a reverse proxy managing your internal
Matrix, Matrix Admin, and Maubot on Docker: The Lean Homelab Stack
Every Matrix homelab guide assumes you want PostgreSQL. The official docs say SQLite is testing-only. Community write-ups default to five containers before you've sent a single message. For a personal server running a handful of users without federation into large public rooms, that's a lot of
Rocky Linux to Docker Host: Cockpit, Docker Engine, and Portainer from a Fresh Install
A fresh Rocky Linux VM sits in your hypervisor doing nothing. You know what it needs to become , a Docker host you can actually operate . The default documentation assumes you already know which pieces belong together, in what order, and why the ones that aren't mentioned still matter.