What Happened: containrrr/watchtower Archived December 17, 2025
On December 17, 2025, the maintainers of the containrrr organization archived the containrrr/watchtower GitHub repository. The repository is now marked "Public archive" and is read-only. No further commits, releases, bug fixes, or security patches will be issued by the containrrr team.
This affects:
- The GitHub repository at
github.com/containrrr/watchtower - The Docker Hub image at
containrrr/watchtower— frozen at version v1.7.1 - All documentation hosted under the containrrr organization
Why Was It Archived?
The containrrr maintainers did not publish a detailed explanation for the archive decision. Based on the public repository history, several factors are observable:
- Declining commit velocity: The pace of commits and releases had slowed significantly in 2024–2025, with v1.7.1 (the final release) shipping in early 2025 after a long gap from v1.7.0.
- Maintainer capacity: Open-source maintainers have limited time, and Watchtower's codebase has grown in complexity as Docker's API and registry landscape evolved.
- Community fork: An active community fork by Nicholas Fedor (
nickfedor/watchtower) had already established itself before the archive, providing a viable continuation path.
This pattern — a major open-source tool archiving when a healthy fork exists — is a common and legitimate outcome. The community carries the project forward.
Does Watchtower Still Work After the Archive?
Yes — for now. The frozen containrrr/watchtower:1.7.1 image still:
- Pulls successfully from Docker Hub
- Connects to the Docker daemon via the socket
- Detects new image digests and updates containers
- Sends notifications via Shoutrrr
However, its continued functionality is not guaranteed over time. The risks of running an archived image grow as:
- Docker Engine releases new API versions that may deprecate or change behavior the image relies on
- Docker Hub and registry APIs evolve — changes to authentication, manifest formats, or rate limiting may break polling
- Alpine Linux base accumulates unpatched CVEs in the Go runtime and OS packages
The image is safe to run today and is likely safe for the near term. It is not recommended for the long term without a migration plan.
What You Should Do
Option 1 — Migrate to nickfedor/watchtower (Recommended)
The nickfedor/watchtower fork is the community-endorsed continuation of Watchtower. Nicholas Fedor, a known contributor to the container tooling ecosystem, has maintained an active fork with continued releases, security patches, and new features.
The migration is one line change in your Docker Compose file:
# Before (archived)
image: containrrr/watchtower
# After (active, recommended)
image: nickfedor/watchtowerAll environment variables, labels, volumes, and ports are identical. See the complete step-by-step migration guide for Docker Run, Docker Compose, and Docker Swarm.
Option 2 — Switch to a Notification-Only Tool
If the archive decision has made you reconsider whether auto-restart is right for your environment, this is a good time to evaluate notification-only tools:
- Diun — detects new images and sends alerts, never restarts automatically
- What's Up Docker — web UI with extensive notification routing, notify-only by default
See the 2026 alternatives guide for a full comparison.
Option 3 — Keep Running the Archived Image (Short Term)
If you cannot migrate immediately, the frozen containrrr image will continue to function in the near term. However, set a maintenance window to migrate within the next 1–3 months. Do not leave this as a permanent solution.
Migration Summary
| Setup Type | Change Required | Time |
|---|---|---|
| Docker Compose | Change image: line; run docker compose up -d | ~2 min |
| docker run | Update image name in command; stop old container first | ~3 min |
| Docker Swarm | Update service image with docker service update | ~5 min |
| Portainer Stack | Edit stack YAML, redeploy via Portainer UI | ~3 min |
Timeline of Events
| Date | Event |
|---|---|
| Early 2025 | containrrr/watchtower v1.7.1 released — final release |
| Mid 2025 | nickfedor/watchtower fork becomes publicly active with new releases |
| December 17, 2025 | containrrr/watchtower GitHub repository archived (read-only) |
| December 2025 – present | nickfedor/watchtower continues active development with patches and releases |
| June 2026 | nickfedor fork is the community-recommended replacement |
Frequently Asked Questions
The original containrrr/watchtower project was archived on December 17, 2025 — that specific project is discontinued in the sense that no new releases will ship from the containrrr organization. However, the community fork nickfedor/watchtower is actively maintained and carries Watchtower forward. Watchtower as a tool is not dead — it changed hands.
Yes, for now. The frozen v1.7.1 image still runs and updates containers. However it receives no security patches, and long-term compatibility with evolving Docker Engine and registry APIs is not guaranteed. Migrate to nickfedor/watchtower at your next opportunity.
For automatic container updates: nickfedor/watchtower is the best replacement — drop-in compatible with continued active development. For notification-only behavior, Diun and What's Up Docker are strong alternatives. See our full alternatives guide.
The containrrr maintainers did not publish a detailed explanation. The repository saw declining commit activity in 2024–2025, and a healthy community fork already existed. This is a common pattern in open-source — maintainers step back, the community carries the project forward.
Yes. Nicholas Fedor is a known contributor in the container tooling community. The fork is fully open-source and auditable at github.com/nicholas-fedor/watchtower. It is the most actively maintained Watchtower image available in 2026. As with any container image you grant Docker socket access, review recent commits before deploying in sensitive environments.
Migrate to nickfedor/watchtower — takes under 2 minutes
The actively maintained Watchtower fork. Fully compatible with your existing configuration.
Migration Guide →