← All projects

Go · Docker · Maintained fork

Lighthouse

A process for automating Docker container base-image updates — a maintained fork of Watchtower, which entered "no longer maintained" status upstream. Lighthouse carries that work forward with ongoing maintenance and security hardening, and stays drop-in compatible.

Go Apache-2.0 drop-in compatible homelab-focused

Picking up where upstream stopped

Watchtower was a beloved tool for keeping containerized apps current — until it stopped being maintained. Rather than let a useful project rot, Lighthouse forks it and keeps it alive: ongoing maintenance, security hardening, and a clean migration path that respects everyone already running it.

How it works

Push a new image to Docker Hub (or your own registry) and Lighthouse pulls it down, gracefully shuts down the running container, and restarts it with the exact options it was originally deployed with.

docker run --detach \
  --name lighthouse \
  --volume /var/run/docker.sock:/var/run/docker.sock \
  grioghar/lighthouse

Drop-in compatible by design

Migration friction is what kills forks. Lighthouse honours every existing WATCHTOWER_* environment variable and com.centurylinklabs.watchtower.* container label, so existing deployments keep working untouched. New deployments can use the LIGHTHOUSE_* variables and lighthouse.* labels instead — and when both are present, the Lighthouse form takes precedence.

Honest scoping: Lighthouse is built for homelabs, media centers, and local dev environments — not commercial production. The README points production users toward Kubernetes (or lighter options like MicroK8s and k3s) rather than overselling itself. Knowing where a tool belongs is part of building it well.
← Back to all projects