Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Self-host What's Up Docker
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
A container update monitor. It connects to the Docker socket (or Swarm, Kubernetes or Nomad), lists the running containers, checks their registries on a schedule (hourly by default) for newer tags or changed digests, and shows what is out of date in a web dashboard and REST API. It can then notify you through triggers (Discord, Slack, Telegram, email, webhooks, MQTT and others) or, if you configure a docker or compose trigger, pull the new image and recreate the container. Sign-in is mandatory, with local users and roles or OpenID Connect. State, including users and update history, is stored in an embedded SQLite file under /store.
Pick What's Up Docker when you run a handful of containers by hand or with Compose and want to know when their images have newer tags, without handing the updates to an agent that restarts things on its own. It reads the Docker socket, compares tags and digests against Docker Hub, GHCR, Quay and other registries, tells major, minor and patch jumps apart, and sends you a notification through any of its 30-plus triggers. Updating is opt-in through a docker or compose trigger. It is MIT-licensed (the repository's LICENSE file is the MIT text), a Node.js app in one Alpine image, with an embedded SQLite database. Our snippet adapts the quick start's compose example, pins `getwud/wud:9.8.0` (released 2026-11-07) instead of `latest`, publishes port 3000, generates the admin password and a session secret into `.env`, and keeps `/store` in a named volume. Choose Watchtower-style auto-updaters if you want updates applied without a dashboard, or Dockge or Portainer if you also want to manage the stacks themselves.
What you need
Any VPS with at least 256 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Paid link — we earn a commission if you shop through it.
Install
Run these commands on your server:
# What's Up Docker (WUD) — container update monitor — adapted from the quick start's compose example, pinned to 9.8.0, with a generated admin password and session secret in .env and a named volume for the /store SQLite databasecat > .env <<EOFWUD_ADMIN_PASSWORD=$(openssl rand -hex 16)WUD_SESSION_SECRET=$(openssl rand -hex 32)EOFcat > docker-compose.yml <<'EOF'services: wud: image: getwud/wud:9.8.0 restart: unless-stopped environment: - WUD_AUTH_ADMIN_USER=admin - WUD_AUTH_ADMIN_PASSWORD=${WUD_ADMIN_PASSWORD} - WUD_AUTH_SESSION_SECRET=${WUD_SESSION_SECRET} ports: - "3000:3000" volumes: - /var/run/docker.sock:/var/run/docker.sock:ro - wud-store:/storevolumes: wud-store:EOFdocker compose up -dtimeout 120 bash -c 'until curl -fsSL -o /dev/null http://localhost:3000/health; do sleep 3; done'# → http://SERVER_IP:3000 — the WUD sign-in page; log in as admin with WUD_ADMIN_PASSWORD from .env (grep WUD_ADMIN_PASSWORD .env), then the dashboard lists the wud container itself
WUD's docs, Dockerfile and release notes flag these before you rely on it:
non-negotiableIt needs the Docker socket, and that is the whole host. Anyone who controls the WUD container has the full Docker API through that socket, and anyone who signs in with an admin or read-write role can start updates once a docker trigger is configured. Our snippet mounts the socket read-only, as the watcher docs' examples do (the quick start does not), but that flag only protects the socket file and does not restrict the API calls made through it. The image has no USER directive, so it runs as root. For anything exposed, the watcher docs describe remote daemons behind a socket proxy or mutual TLS.
non-negotiableSign-in is mandatory and anonymous access is disabled. If no administrator exists and neither the bootstrap variables nor an OIDC admin group is set, WUD refuses to start rather than run open. Our snippet bootstraps admin from WUD_AUTH_ADMIN_USER and WUD_AUTH_ADMIN_PASSWORD; the password sits in .env and in the container's environment. WUD re-applies those variables to the account on every start, so a password changed from My Profile reverts at the next restart. To rotate it, change .env and recreate the container. Setting WUD_AUTH_SESSION_SECRET (32+ characters) keeps browser sessions valid when the container is recreated.
non-negotiableBy default WUD only reports. Updates happen only if you configure a docker or compose trigger; its DRYRUN option pulls but never recreates, which is the safer first step. The default watch schedule is hourly (0 * * * *), and the docs warn about Docker Hub rate limits, so digest watching is off for Hub images unless you turn it on.
non-negotiableState lives in /store/wud.sqlite. Without a volume on /store, users and history vanish with the container. Upgrades from the old LokiJS format migrate automatically and rename wud.json to wud.json.migrated, so back up the volume before moving between major versions.
non-negotiableThe Docker Hub repository carries moving tags next to releases: latest, 9 and 9.8, plus branch builds such as main and fix-… pushed the same day as the release. Pin the exact version tag like we do and read the release notes before bumping; 9.8.0 adds an XMPP trigger and changes how SemVer differences behind floating tags are detected.
non-negotiableWUD serves plain HTTP on port 3000. Put a reverse proxy with TLS in front of it before exposing the dashboard, because it carries login credentials and API tokens.
What's Up Docker used 114 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 256 MB.
Is the What's Up Docker install snippet verified?
The What's Up Docker install snippet is marked verified on Ubuntu 26.04 (Nov 2026).