nicholas-fedor/watchtower

Automate Docker container image updates

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 35 minutes ago
Added to GitGenius on September 15th, 2026
Created on January 16th, 2025
Open Issues & Pull Requests: 16 (+0)
GitHub issues: Enabled
Number of forks: 76
Total Stargazers: 4,474 (+0)
Total Subscribers: 15 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.4 hours
Mean response time: 20.1 hours
90th percentile: 21.6 hours
Tracked items: 212

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 3% of issues opened in the past year have never received a reply. 91% of issues opened in the past year have since been closed. Three people close 92% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 16
New in 7 days: 7
Closed in 7 days: 2
Avg open age: 134 days
Stale 30+ days: 6
Stale 90+ days: 3

Recent activity

Opened in 7 days: 7
Closed in 7 days: 2
Comments in 7 days: 6
Events in 7 days: 26

Top labels

  • bug (124)
  • enhancement (30)
  • Notifications (6)
  • Podman (5)
  • documentation (3)

Detailed Description

Watchtower is a tool that automates Docker container image updates by monitoring registries and redeploying containers when new images are available.

The tool solves the problem of keeping containerized applications up to date without manual intervention. When you push a new image to Docker Hub or a private registry, Watchtower detects the change, pulls the new image, gracefully shuts down the existing container, and restarts it with the same configuration options that were originally used. This eliminates the need for manual container management workflows.

Watchtower is designed for homelabs, media centers, and local development environments rather than production systems. The README explicitly recommends against using it in commercial or production environments, suggesting Kubernetes with CI/CD pipelines as the appropriate alternative for those contexts. The tool requires Docker and has been tested with Docker versions from 1.43 onward, with support for multiple architectures including amd64, i386, armhf, arm64v8, and riscv64. It handles Docker API version negotiation automatically by default, though this can be overridden with explicit configuration.

Development activity shows a community-driven project with contributions from multiple developers. The project maintains comprehensive documentation separate from the README and actively supports a range of hardware architectures, indicating attention to accessibility across different deployment scenarios.