Introduction
Open source container update monitoring built in TypeScript. Auto-discover containers, detect image updates across 23 registries, and trigger notifications via 20+ services.
Drydock monitors your Docker containers for image updates. It auto-discovers running containers, checks 23 registries for new versions, and triggers notifications or automated updates via 20+ services.
🔍 How it works
🐳 Watchers scan Docker hosts to discover containers to monitor.
📦 Registries query remote Docker registries to find update candidates.
⚡ Triggers perform actions when updates are available — notify, update, or run custom scripts.
✨ Key features
- 🔎 Auto-discovery of running containers
- 📦 23 registry integrations (Docker Hub, GHCR, ECR, GCR, GAR, GitLab, Quay, and more)
- 🔔 20+ trigger types (Slack, Discord, Telegram, SMTP, webhooks, Docker auto-update, and more)
- 🧪 Dry-run preview before applying updates
- 💾 Image backup and one-click rollback
- 🔄 Auto-rollback on health check failure
- 🪝 Pre/post-update lifecycle hooks
- 🔁 Graceful self-update
- 🌐 Distributed agents for remote Docker hosts
- 📊 Prometheus metrics and Grafana dashboard
- 🔐 OIDC authentication support
- 🛡️ Update Bouncer — vulnerability scanning, signature verification, and SBOM
- 🛠️ Full REST API, webhooks, and audit log
🚀 Quick start
docker run -d --name drydock \
-v /var/run/docker.sock:/var/run/docker.sock \
-p 3000:3000 \
codeswhat/drydockDirect socket access grants the container full control over the Docker daemon. See the Quick Start guide for the recommended socket proxy setup and other secure connection options.
📚 Next steps
- Configure registries — set up private image access
- Set up triggers — enable notifications and auto-updates
- Configure webhooks — integrate with CI/CD pipelines
- Lifecycle hooks — run commands before and after updates
- Backup & rollback — automatic backups and one-click restore
- Enable authentication — secure your instance
- Monitor with Prometheus — add observability