What this site is
WatchtowerDocker is a reference hub for Watchtower, the free, open-source tool that automatically updates Docker containers when new images are published. We write installation guides, configuration references, platform-specific setup instructions, and troubleshooting articles for people running Watchtower in homelabs and production environments.
We are an independent publisher. We do not control, maintain, or speak for the Watchtower codebase itself — that work belongs to the original containrrr/watchtower project and the community fork at nicholas-fedor/watchtower. If a page on this site ever reads as though it's the "official" project, that's a mistake — please let us know and we'll fix it.
How we make money
This site is supported by display advertising. We don't charge for any guide, we don't have a paid tier, and we don't collect signups. If you ever see a pricing page or "Start Free Trial" button on this domain, treat it as a bug — this site doesn't sell anything.
Who writes the articles
Articles are written and maintained by the WatchtowerDocker editorial team. We're a small independent operation, not a company with named on-staff engineers — earlier versions of this site used individual bylines with invented names and titles, which was inaccurate, and we've since replaced them with this single, honestly-labeled byline across every article.
Editorial & accuracy policy
- We link primary sources. Claims about the Watchtower project's status (e.g. the containrrr archive) link directly to the GitHub repository or discussion thread they're based on, so you can verify them yourself.
- We don't fabricate statistics, testimonials, or endorsements. If we can't verify a number or a claim of endorsement, we don't publish it.
- We correct mistakes. Articles carry a "last reviewed" date where relevant, and are updated when the underlying project changes (as happened with the containrrr archive in December 2025).
- We flag uncertainty. Where something is our own assessment rather than a documented fact — like which fork is most actively maintained — we say so explicitly instead of presenting opinion as fact.
Contact
Found an error, a broken link, or a claim that doesn't hold up? Open an issue against the article on our blog index page or reach out via the project links in the footer. We'd rather fix a mistake than leave it up.