v1.7.1 stable v1.8 RC available to test
Know what changed before anything updates
Drydock watches your Docker containers and 23 registries, tells you what's outdated and whether it's major, minor, patch or digest, and updates only when you say so. Scans, backups and rollback are built in. Self-hosted, MIT licensed.

- 23 registries
- 21 triggers
- 100% TS coverage
- 279 stars
- 902K downloads
- 14 forks
- 9 open issues
- Sponsor
Coverage scope: CI enforces 100% line, branch, function and statement coverage on the backend sources and UI TypeScript files. Vue components have separate aggregate floors, and vue-tsc typechecks scripts and templates without establishing runtime coverage.
Batteries included
See it, check it, then update it
Watch, scan, approve, back up, roll back. All of it ships in the MIT image, with no paid tier.
Core
- Auto-Discovery
Automatically discovers running containers and tracks their image versions without manual configuration.
- Distributed Agents
Monitor remote Docker hosts via SSE-based agents. Centralized dashboard for all environments.
- Prometheus Metrics
Built-in /metrics endpoint with Grafana dashboard template. Full observability out of the box.
- Container Grouping
Smart stack detection via compose project or labels. Collapsible groups with batch actions.
Security
- Update Bouncer
Trivy or Grype scanning blocks unsafe updates before they deploy. Adds cosign signature checks and CycloneDX and SPDX SBOMs.
- Audit Log
Event-based audit trail with persistent storage. Full REST API and Prometheus counters.
- OIDC Authentication
Secure your instance with OpenID Connect. Works with Authelia, Auth0, and Authentik.
Integrations
- 23 Registries
Query Docker Hub, GHCR, ECR, GCR, GAR, GitLab, Quay, LSCR, ACR, Harbor, Artifactory, Nexus, and more.
- 21 Triggers
Notify via Slack, Discord, Telegram, Teams, SMTP, MQTT, HTTP, Gotify, NTFY, Kafka, and more.
- Webhook API
Token-authenticated HTTP endpoints for CI/CD integration. Trigger updates on demand.
Operations
- Dry-Run Preview
Preview what an update would do before it touches a container. Turn on DRYRUN first, then switch it off when you trust the result.
- Image Backup
Keeps the previous image before each update (3 by default, configurable), so you can roll back in one click.
- Approval Queue
Hold updates for a human to approve before anything runs. Available in the v1.8 release candidate.
- Auto Rollback
Rolls back on its own when the new container fails its health check. Set dd.rollback.auto=true to keep watching after the update.
- Container Actions
Start, stop, restart and update containers from the UI or API. On by default; set DD_SERVER_FEATURE_CONTAINERACTIONS=false to turn it off.
15 of 15 capabilities
Get running
Try it in one command
The quick start turns auth off for a local look (DD_ANONYMOUS_AUTH_CONFIRM=true). With no auth setting at all, Drydock refuses requests on purpose. The hardened compose file is the one to run.
$ docker run -d \
--name drydock \
-v /var/run/docker.sock:/var/run/docker.sock \
-v drydock-store:/store \
-e DD_ANONYMOUS_AUTH_CONFIRM=true \
-p 3000:3000 \
codeswhat/drydockHeads upMounts the Docker socket directly and runs with anonymous auth. Fine for a local try, not for production.
Screenshots
See it in action
The real Drydock interface, running live with sample data. No install required.
Connecting to the live demo…
Open demo directlyOpen the full demo . Sample data resets in your browser; this is the same UI shipped with Drydock.
On the horizon
Roadmap
Where we've been and where we're headed.
│Swarm and Kubernetes watchers
│GitOps sync
│+2 moreshow less
│Health gates and canary deploys
│RBAC and LDAP/AD
│Per-update-type candidates and running-version ceilings
│Watcher include/exclude filters
│+2 moreshow less
│Audit actor and export
│Home Assistant and Homepage integrations
│Landed: drydock.yml configuration with environment overrides
│Landed: revision-checked editors for selected local file-owned settings
│+3 moreshow less
│Landed: fleet bulk actions with confirmation and bounded update concurrency
│Landed: SQLite persistence and one-time legacy JSON import
│Landed: Images page with inventory and prune
│Dependency-aware update ordering
│Per-action update policy
│+2 moreshow less
│Keyboard shortcuts and PWA
│Legacy DD_TRIGGER_* variables removed
│Stable maintenance and security fixes from the 1.6.1 candidate train
│Notification templates and preferences
│Declarative and maturity policy workflows
│+1 moreshow less
│Dashboard, responsive table/card views, and consistent resource-action toolbars
│Recreation-safe maturity policy retention
│Pinned-tag digest detection and informational insights
│+1 moreshow less
│Tag-policy inheritance and visibility refinements
Show 8 earlier releasesHide earlier releases
│Security, registry, and secret-handling fixes
│Maturity gate and maintenance-window reliability
│+1 moreshow less
│Container detail polish and final i18n coverage
│Live observability and notification workflows
│Dashboard customization and design-system refresh
│+2 moreshow less
│Localized UI and edge-agent foundation
│Bulk scan and update eligibility workflows
│Headless mode
│Maturity-based update policy
│+1 moreshow less
│Agent and login polish
│Modern UI shell and command palette
│Compose-native YAML-preserving updates
│+2 moreshow less
│Compose-safe updates and stronger rollback flows
│Self-update controller and dashboard customization
│Trivy vulnerability scanning
│Update Bouncer deployment gate
│+2 moreshow less
│SBOM generation
│Cosign signature verification
│Audit log and REST API
│Image backup and rollback
│+2 moreshow less
│Container actions and webhooks
│Lifecycle hooks, maintenance windows, and metrics
│Application log viewer
│Agent log source selector
│+1 moreshow less
│Container log access
│TypeScript app foundation
│ReDoS and XSS hardening
│+1 moreshow less
│Vitest migration and broader coverage
Why Drydock
How we compare
How Drydock stacks up against WUD, Diun and Watchtower (archived December 2025). Rows come from the README matrix, including one where WUD wins.
| Feature | Drydock | WUD | Diun | WatchtowerArchived |
|---|---|---|---|---|
| Web UI / dashboard | Yes | Yes | No | No |
| Semver-aware updates | Yes | Yes | Partial | No |
| Image backup & rollback | Yes | Partial | No | No |
| Vulnerability scanning | Yes | No | No | No |
| Distributed agents | Yes | Partial | No | Partial |
| RBAC / multi-user roles | No | Yes | No | No |
Probably not for you yet: Swarm, Kubernetes and Nomad watchers, RBAC and multi-user roles, and a one-shot CI mode. Swarm, Kubernetes and RBAC are planned for v2.0 and later. If you need any of them today, WUD is the closer fit.
Switching: coming from WUD? The config migrate --dry-run --file compose.yml command previews the rewrite of your WUD_* variables and wud.* labels to DD_* and dd.*, but it only sees files inside the container, so mount your Compose folder first. The WUD comparison has the full command. Coming from Watchtower, which was archived in December 2025? Read the Watchtower comparison or the WUD comparison.
Ecosystem
Part of the CodesWhat stack
Drydock is one piece of a small, focused toolkit — each tool does one job, and they compose.

Container update monitoring

Scoped Docker socket proxy

Secure remote Docker agent
FAQ
Frequently asked questions
Common questions about how Drydock works and how it fits into your stack.
On every poll cycle Drydock reads the image reference and current digest from each watched container, then queries the upstream registry for available tags. It applies your per-container tag filters (dd.tag.include / dd.tag.exclude regex patterns compiled with re2js for linear-time evaluation) and semantic-version ordering to determine the latest eligible tag. If the latest digest differs from the running one, the container is flagged as having an available update. SSE keeps connected browser sessions in sync in real time without polling on the client side.
Drydock ships with 23 registry providers: Docker Hub, GitHub Container Registry (GHCR), Amazon ECR, Google Container Registry (GCR), Google Artifact Registry (GAR), GitLab Registry, Red Hat Quay, LinuxServer Container Registry (LSCR), Azure Container Registry (ACR), Harbor, JFrog Artifactory, Sonatype Nexus, Gitea, Forgejo, Codeberg, and more — plus a generic private-registry provider for anything that speaks HTTP Basic or bearer token auth. TLS customization (CA file, insecure skip-verify) is available on every provider.
Drydock watches every container by default. Add dd.watch=false to opt a container out, or set DD_WATCHER_{name}_WATCHBYDEFAULT=false to flip that watcher to opt-in mode, where only containers labeled dd.watch=true are watched. Use dd.tag.include with a regex to restrict which tags are eligible — for example dd.tag.include=^\d+\.\d+\.\d+$ to match only semver tags. dd.tag.exclude filters out tags that match. dd.tag.transform applies a rewrite to the tag string before matching. dd.display.name overrides the container name shown in the dashboard, and dd.group groups containers into collapsible stacks.
Watchtower auto-updates containers on a schedule with minimal config and no UI, and it was archived in December 2025. Drydock is an update management platform: it detects what is available, shows you a dashboard, lets you preview and approve changes, backs up images before applying them, and rolls back automatically if the new container fails its health check. It also adds security scanning (Grype/Trivy CVEs, SBOM generation, Cosign signature verification) and per-container update policies. If you want silent automatic updates, Watchtower is simpler. If you want visibility, control, security gates, and notification integrations, Drydock fits better.
No. The recommended setup puts a socket proxy (tecnativa/docker-socket-proxy or sockguard) in front of the socket, so Drydock only reaches the Docker API endpoints you allow. Read-only watching needs CONTAINERS, IMAGES, EVENTS, SERVICES and INFO. Add POST=1 and NETWORKS=1 only if you want container actions and auto-updates. Mounting /var/run/docker.sock directly works for a quick local try, but it hands Drydock the whole Docker API.