Quick answer

Watchtower (containrrr/watchtower) is no longer maintained: its repository is archived, the README opens with a notice saying so, and the last release, v1.7.1, was in November 2023. Its docs describe it pulling new images and restarting containers, but nobody is fixing it, I haven’t run it, and an open issue reports it failing on Docker Engine 29.0.0. Its maintainers say forks exist, that they can’t vouch for them, and that one of them wouldn’t advise using the active forks he had looked at.

Contents

At a glance

Class
Tutorial

Provenance

  • Nov 18, 2026Published

Watchtower is archived. The containrrr/watchtower repository is read-only on GitHub, its README opens with “This project is no longer maintained,” and the last tagged release is v1.7.1 from November 11, 2023. The last commit, on December 17, 2025, only added that notice. If you came here to install it, the project’s docs still show you how to run it, but nobody is going to fix it, and you should know what that means before you hand it control of your containers.

What the project says about itself

The notice points to a GitHub discussion, “Goodbye containrrr/watchtower!”, posted December 17, 2025 by one of the two maintainers. They say they are looking to archive the repository because neither of them is a big Docker user anymore, and they lost interest and time. They also say there are a few forks, that they know nothing about them and can’t vouch for their legitimacy, and that anyone who wants to keep using Watchtower should assess a fork themselves. The poster also says a few of the active forks he had looked at are poor quality and that, while they might work, he wouldn’t advise using any of them. He doesn’t name them, so I can’t say whether that applies to the fork below.

So there is no successor the project endorses. It points at no fork. Forks do exist. One, nicholas-fedor/watchtower, published its v1.24.0 on November 4, 2026, ships its image as nickfedor/watchtower, and says in its README that it was tested against Docker API v1.43 and higher and negotiates the API version by default. I have not reviewed its code, and the original maintainers’ warning applies to it as much as any other: read what you are about to give your Docker socket to.

What Watchtower does

Per its documentation, Watchtower monitors your running containers and watches for changes to the images they were started from. When an image has changed, it pulls the new image, gracefully shuts down the existing container, and restarts it with the same options that were used when it was deployed initially. By default it watches all containers on the daemon it points at, and by default it checks every 24 hours.

It is itself a container, and it needs the Docker API to do any of this, so the docs have you mount /var/run/docker.sock into it.

A compose example from the docs

This is the compose file from the project’s quick start, except that I dropped its version: "3" line, which Docker’s docs say is obsolete and only produces a warning.

services:
  watchtower:
    image: containrrr/watchtower
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

That is a complete Watchtower. With no arguments it checks all running containers every 24 hours and updates any whose image has changed. To change that behavior you add arguments or environment variables. This version uses the environment variable names from the project’s arguments page; I assembled it from that page and haven’t run it:

services:
  watchtower:
    image: containrrr/watchtower
    environment:
      TZ: America/Chicago
      WATCHTOWER_SCHEDULE: "0 0 4 * * *"
      WATCHTOWER_CLEANUP: "true"
      WATCHTOWER_LABEL_ENABLE: "true"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

  someapp:
    image: example/someapp:latest   # replace with your own image
    labels:
      - "com.centurylinklabs.watchtower.enable=true"

If you keep your variables in a .env file instead, Docker Compose environment variables covers how Compose reads them.

The options that matter

All of these are from Watchtower’s arguments and container-selection pages.

What you wantOptionDefault and notes
Check on a clock--schedule, WATCHTOWER_SCHEDULEA cron expression with six fields (not the usual five), for example 0 0 4 * * *. Use it or --interval, not both.
Check every N seconds--interval, WATCHTOWER_POLL_INTERVAL86400 seconds (24 hours).
Time zone for logs and the scheduleTZUTC unless set. Set it, or your 4 a.m. schedule is 4 a.m. UTC.
Delete the old image after an update--cleanup, WATCHTOWER_CLEANUPOff. The docs say it prevents orphaned images accumulating. See Docker cleanup for what else eats disk.
Check and notify, but don’t update--monitor-only, WATCHTOWER_MONITOR_ONLYOff. Per container: label com.centurylinklabs.watchtower.monitor-only=true. The docs note the latest image is still pulled so it can tell what changed.
Only update containers you opt in--label-enable, WATCHTOWER_LABEL_ENABLEOff. With it on, only containers labeled com.centurylinklabs.watchtower.enable=true are watched.
Exclude one containerlabel com.centurylinklabs.watchtower.enable=false on that containerSet on the container to ignore, not on Watchtower.
Exclude by name--disable-containers, WATCHTOWER_DISABLE_CONTAINERSExcludes the listed names even if they carry the enable label.
Update once and exit--run-onceRuns an update attempt on the container names you pass and exits.
Remove anonymous volumes on update--remove-volumesOff. Named volumes are not removed.

Two details from those pages are easy to miss. First, arguments take precedence over labels by default, so a global --monitor-only beats a container’s monitor-only=false label unless you also set --label-take-precedence. Second, --remove-volumes is off by default and removes anonymous volumes only, the same category the Docker cleanup page shows can hold real data when you never named a volume.

I found no mention of rollback in the project’s documentation. Think of an update as a one-way move, and back up anything stateful before it runs unattended.

What the project says about production

Plainly: don’t. The README says Watchtower is intended for homelabs, media centers and local dev environments, and that the project does not recommend using it in a commercial or production environment. It points those users to Kubernetes, or to MicroK8s and k3s if Kubernetes is too big a step.

Two things from Docker’s side are worth knowing alongside that.

The socket. Mounting docker.sock is what lets Watchtower work, and it is control of the Docker daemon. Docker’s security page says only trusted users should be allowed to control the daemon, and that a container can be started with the host’s / shared into it. That is the page’s reasoning for the daemon in general, not a statement about Watchtower, and I’d weigh it that way for any container you give the socket.

Current Docker Engine. Docker’s release notes say Engine 29.0.0 (November 10, 2025) raised the daemon’s minimum API version to 1.44, and 29.3.0 (March 5, 2026) lowered it to 1.40. Watchtower’s arguments page gives its default API version as 1.24. An issue opened November 14, 2025 against the repository, still open today, reports the error “client version 1.25 is too old” on Docker 29.0.0. Both Watchtower numbers are below 1.40, so I would not assume it runs on a current daemon. I haven’t tested it. People in that thread report setting the DOCKER_API_VERSION variable (the arguments page lists it) as a workaround; the project’s docs say nothing about this, and the repository is archived, so don’t expect an official answer. Check docker version on your host before relying on it.

Docker Hub limits

Watchtower polls registries, and Docker Hub rate-limits pulls. Docker’s documentation says unauthenticated users get 100 pulls per six hours per IPv4 address or IPv6 /64 subnet, authenticated Docker Personal users get 200, and paid plans have no pull rate limit. It also says version checks do not count towards usage pricing, and that in its rate-limit check a HEAD request doesn’t count where a GET does. Watchtower’s docs say its HEAD digest check lets it skip pulling when nothing changed, and the default of its --warn-on-head-failure option (auto) warns about failed HEAD requests to registries known to handle them that may rate-limit pulls, mainly docker.io. I haven’t measured how many pulls a given Watchtower setup triggers. As for the free question, Docker’s pricing page lists Docker Personal at $0, with those limits.

Alternatives, described from their own documentation

ToolWhat its docs say it doesStatus I found on 2026-11-17
DiunIt “watches container images and tells you when an update is available.” It checks registries for new tags or digest changes and notifies you. Its README describes notifications, not applying updates.Not archived; v4.33.1 released October 24, 2026; MIT.
What’s Up Docker (WUD)Monitors containers across Docker, Compose, Swarm, Kubernetes and Nomad, does semantic-version analysis and tag filtering, and notifies. The README also lists automated updates: pulling new images and recreating containers on demand for Docker, Compose and Nomad.Not archived; 9.8.0 released November 7, 2026; MIT.
Podman auto-updatepodman auto-update pulls new images and restarts containers configured for auto-updates. Containers must run inside a systemd unit and carry the io.containers.autoupdate label. It ships a podman-auto-update.service triggered daily at midnight by a timer, and has a --dry-run option.Part of Podman; requires Podman, not Docker.
Forks of Watchtowernicholas-fedor/watchtower is one: same idea, own image name, see above.v1.24.0 released November 4, 2026; Apache-2.0. The original maintainers do not vouch for any fork.
Manual composedocker compose pull pulls service images; docker compose up recreates a container when its configuration or image changed, preserving mounted volumes.Part of Docker Compose.

The choice is mostly about who decides when an update lands. If you want to know about updates and apply them yourself, Diun, or Watchtower in monitor-only mode, fit that, and the manual compose route costs you two commands. If you want unattended updates, WUD is the closest tool I found that lists automated updates in its README, and Podman covers it natively if you run Podman. A Watchtower fork is the other candidate, with the maintainers’ warning above attached. For anything that matters, I’d rather get the notification and do the update on a day I’m watching. A web UI for your stacks is a different tool again; Komodo, Portainer and Dockge compared and the Dockge walkthrough cover that side, and the Docker RAM planner will tell you what a stack costs in memory before you add more containers.

Frequently asked questions

Is Watchtower discontinued?
Yes, as far as its original maintainers go. The containrrr/watchtower repository is archived on GitHub, and its README starts with ‘This project is no longer maintained’ and links to a discussion titled ‘Goodbye containrrr/watchtower!’ (December 17, 2025). In it the two maintainers say they are no longer big Docker users and lost interest and time for maintaining it. The last release, v1.7.1, is dated November 11, 2023.
What is Watchtower in Docker?
A container that watches your other running containers. Its documentation says it monitors the images those containers were started from and, when an image has changed, pulls the new one, shuts the old container down gracefully and restarts it with the same options it was originally started with. You give it access to the Docker API by mounting /var/run/docker.sock into it.
How do I run Watchtower with Docker Compose?
The project’s docs give a compose file with one service: image containrrr/watchtower and a volume mapping /var/run/docker.sock to /var/run/docker.sock. Everything else is optional: set WATCHTOWER_SCHEDULE for a six-field cron time, WATCHTOWER_CLEANUP to remove old images, and WATCHTOWER_LABEL_ENABLE if you only want containers you have labeled. The full example and the options are further down this page.
Is there a Docker Watchtower alternative?
It depends on whether you want updates applied or only announced. Diun watches registries and notifies you, and its README does not describe it updating containers. What’s Up Docker (WUD) monitors and can also update Docker and Compose containers through triggers. Podman has built-in auto-update for containers run under systemd. The plain Docker route is docker compose pull then docker compose up -d. Forks of Watchtower also exist; the original maintainers say they can’t vouch for them, and one says he wouldn’t advise using the active forks he looked at.
Does Docker Hub have a free tier?
Docker’s pricing page lists Docker Personal at $0, but Docker’s pull-limit documentation says unauthenticated and Docker Personal users are subject to pull rate limits per six hours: 100 pulls per IPv4 address or IPv6 /64 subnet unauthenticated, and 200 for an authenticated Personal user. Docker says paid plans have no pull rate limit.
Should I use Watchtower in production?
Its own README says no. Watchtower is intended for homelabs, media centers and local dev environments, and the project says it does not recommend it in a commercial or production environment; it points to Kubernetes, or to MicroK8s and k3s if Kubernetes feels like too big a step.
Does Watchtower work with the current Docker Engine?
I haven’t tested it. Docker’s release notes say Engine 29.0.0 (November 10, 2025) raised the daemon’s minimum API version to 1.44 and 29.3.0 (March 5, 2026) lowered it to 1.40. Watchtower’s docs give its default API version as 1.24, and an issue opened November 14, 2025 on the archived repository reports the error ‘client version 1.25 is too old’ against Docker 29.0.0. Check docker version on your host and read that issue before you rely on it.

Sources and corrections

Last updated
Methodology
See our methodology for research and review standards. It draws on 18 cited sources, listed below, each checked against the original page on 2026-11-17. Read on 2026-11-17: the containrrr/watchtower repository (README, archive flag and latest release from the GitHub API, the docs folder at the main branch, checked against containrrr.dev/watchtower), the maintainers’ discussion #2135, issue #2126; the READMEs of nicholas-fedor/watchtower, crazy-max/diun and getwud/wud; Podman’s podman-auto-update manual; and Docker’s documentation for Compose, the Docker Hub pull limits, the Engine 29 release notes and the daemon security page. I did not install or run Watchtower or any of the alternatives and ran no command for this page. The compose files below combine the project’s documented example with options from its arguments page; I did not run them. The note about Docker Engine 29 compares two published numbers and is not a test.
Corrections
Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.

About the author

I am Lowell K. Wood IV. I research, write and maintain everything on TechFuelHQ from St. Louis County, Missouri.