A lightweight, self-hosted web UI for monitoring Docker container versions, checking for updates, and applying or rolling back changes — with live progress feedback and persistent version history.

• Dashboard overview — stat cards, configuration status, live countdown to next check
• Three update strategies — auto-detected from labels, no manual mapping required
• Live progress modal — real-time log output for every update, rollback, and check
• Health-check gating — automatic rollback if a container fails to become healthy
• Full version history — roll back to any previous version, not just the last one
• History export / import — download a JSON backup before migrations, restore after
• In-UI settings — adjust check interval, history limit, pre-releases, and auto-update without editing compose files
• Dark / light mode — persisted per browser
• ntfy notifications — updates available, success, and failure alerts
• Persistence check — warns on startup and in the UI if /data is not bind-mounted

services:
  dummy:
    image: donaldwin/dummy:latest
    container_name: dummy
    restart: unless-stopped
    ports:
      - "5000:5000"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /path/to/data/dummy:/data          # required for persistent history
      # - /path/to/.env:/env/.env          # add if using Mode 3 (env file)
    environment:
      - TZ=Pacific/Auckland
      - NTFY_ENDPOINT=http://ntfy:80       # optional
      - NTFY_TOPIC=DockerUpdate

Open http://your-server:5000. Then add dummy.enable=true to any container you want monitored.

The minimum to monitor any container:

labels:
  - dummy.enable=true

DUMMY detects the image, polls the registry, and shows updates in the UI. No env files, no compose edits, no VERSION_VARS to configure.

DUMMY automatically selects a strategy based on which labels are present. You can mix strategies across containers.

DUMMY pulls the new image and recreates the container via the Docker SDK, preserving all config — volumes, ports, networks, env vars, restart policy, capabilities, and network aliases.

services:
  radarr:
    image: lscr.io/linuxserver/radarr:6.0.4.10291
    labels:
      - dummy.enable=true

⚠️ Running docker compose up manually after an API-mode update will revert the tag to whatever is in your compose file. Use Mode 2 or 3 if you need files kept in sync.

DUMMY edits the image tag directly in your docker-compose.yml and runs docker compose up -d <service>. Your compose file always reflects the running version.

services:
  sonarr:
    image: lscr.io/linuxserver/sonarr:${SONARR_VER}
    labels:
      - dummy.enable=true
      - dummy.compose_file=/compose/docker-compose.yml
      # - dummy.compose_service=sonarr   # optional if name differs from container

Add to DUMMY's volumes:

- /path/to/your/docker-compose.yml:/compose/docker-compose.yml

DUMMY updates a version variable in your .env file and restarts the container. Ideal when you pin versions as variables and reference them in compose like image: radarr:${RADARR_VER}.

services:
  prowlarr:
    image: lscr.io/linuxserver/prowlarr:${PROWLARR_VER}
    labels:
      - dummy.enable=true
      - dummy.env_var=PROWLARR_VER

Add to DUMMY's volumes:

- /path/to/your/.env:/env/.env

Modes 2 and 3 work together — DUMMY updates both files in one operation:

labels:
  - dummy.enable=true
  - dummy.compose_file=/compose/docker-compose.yml
  - dummy.env_var=PROWLARR_VER

Click the ⚙ Settings button to adjust these without touching your compose file:

Settings are persisted in the SQLite database and survive container restarts. They take precedence over environment variables, so you can set a sensible default via env and override it from the UI at any time.

Settings that cannot be changed from the UI at runtime:

These set the initial defaults. The UI settings panel takes precedence once saved.

Every update and rollback waits for the container to become healthy before marking it as complete. If the container fails to reach a healthy state within HEALTH_CHECK_TIMEOUT seconds, DUMMY:

1. Automatically reverts to the previous version
2. Restarts the container on the old version
3. Sends a failure notification via ntfy (if configured)

The previous image is always retained locally so rollbacks are instant — no re-pull needed.

DUMMY stores the last N versions per container (configurable). In the UI each container shows its history with a ↩ Restore button on every past entry. You can roll back to any recorded version, not just the most recent.

Before migrating your stack or rebuilding your Pi, export a backup:

curl http://your-server:5000/api/history/export -o dummy-history.json

Or use the ↓ Export History button in the UI. To restore after:

curl -X POST http://your-server:5000/api/history/import \
  -H "Content-Type: application/json" \
  -d @dummy-history.json

Re-importing is safe — duplicate entries are skipped.

DUMMY auto-detects the registry from the image name:

DUMMY automatically links the changelog for common images. The following are recognised without any configuration:

linuxserver/* · immich-app/immich · gethomepage/homepage · FlareSolverr/FlareSolverr · advplyr/audiobookshelf · AdguardTeam/AdGuardHome · binwiederhier/ntfy · Plex Media Server · qBittorrent · jellyfin/jellyfin · portainer/portainer

Override or add extras using the CHANGELOG_URLS environment variable or the dummy.changelog label.

A lightweight, self-hosted web UI for monitoring Docker container versions, checking for updates, and applying or rolling back changes — with live progress feedback and persistent version history.

• Dashboard overview — stat cards, configuration status, live countdown to next check
• Three update strategies — auto-detected from labels, no manual mapping required
• Live progress modal — real-time log output for every update, rollback, and check
• Health-check gating — automatic rollback if a container fails to become healthy
• Full version history — roll back to any previous version, not just the last one
• History export / import — download a JSON backup before migrations, restore after
• In-UI settings — adjust check interval, history limit, pre-releases, and auto-update without editing compose files
• Dark / light mode — persisted per browser
• ntfy notifications — updates available, success, and failure alerts
• Persistence check — warns on startup and in the UI if /data is not bind-mounted

services:
  dummy:
    image: donaldwin/dummy:latest
    container_name: dummy
    restart: unless-stopped
    ports:
      - "5000:5000"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /path/to/data/dummy:/data          # required for persistent history
      # - /path/to/.env:/env/.env          # add if using Mode 3 (env file)
    environment:
      - TZ=Pacific/Auckland
      - NTFY_ENDPOINT=http://ntfy:80       # optional
      - NTFY_TOPIC=DockerUpdate

Open http://your-server:5000. Then add dummy.enable=true to any container you want monitored.

The minimum to monitor any container:

labels:
  - dummy.enable=true

DUMMY detects the image, polls the registry, and shows updates in the UI. No env files, no compose edits, no VERSION_VARS to configure.

DUMMY automatically selects a strategy based on which labels are present. You can mix strategies across containers.

DUMMY pulls the new image and recreates the container via the Docker SDK, preserving all config — volumes, ports, networks, env vars, restart policy, capabilities, and network aliases.

services:
  radarr:
    image: lscr.io/linuxserver/radarr:6.0.4.10291
    labels:
      - dummy.enable=true

⚠️ Running docker compose up manually after an API-mode update will revert the tag to whatever is in your compose file. Use Mode 2 or 3 if you need files kept in sync.

DUMMY edits the image tag directly in your docker-compose.yml and runs docker compose up -d <service>. Your compose file always reflects the running version.

services:
  sonarr:
    image: lscr.io/linuxserver/sonarr:${SONARR_VER}
    labels:
      - dummy.enable=true
      - dummy.compose_file=/compose/docker-compose.yml
      # - dummy.compose_service=sonarr   # optional if name differs from container

Add to DUMMY's volumes:

- /path/to/your/docker-compose.yml:/compose/docker-compose.yml

DUMMY updates a version variable in your .env file and restarts the container. Ideal when you pin versions as variables and reference them in compose like image: radarr:${RADARR_VER}.

services:
  prowlarr:
    image: lscr.io/linuxserver/prowlarr:${PROWLARR_VER}
    labels:
      - dummy.enable=true
      - dummy.env_var=PROWLARR_VER

Add to DUMMY's volumes:

- /path/to/your/.env:/env/.env

Modes 2 and 3 work together — DUMMY updates both files in one operation:

labels:
  - dummy.enable=true
  - dummy.compose_file=/compose/docker-compose.yml
  - dummy.env_var=PROWLARR_VER

Click the ⚙ Settings button to adjust these without touching your compose file:

Settings are persisted in the SQLite database and survive container restarts. They take precedence over environment variables, so you can set a sensible default via env and override it from the UI at any time.

Settings that cannot be changed from the UI at runtime:

These set the initial defaults. The UI settings panel takes precedence once saved.

Every update and rollback waits for the container to become healthy before marking it as complete. If the container fails to reach a healthy state within HEALTH_CHECK_TIMEOUT seconds, DUMMY:

1. Automatically reverts to the previous version
2. Restarts the container on the old version
3. Sends a failure notification via ntfy (if configured)

The previous image is always retained locally so rollbacks are instant — no re-pull needed.

DUMMY stores the last N versions per container (configurable). In the UI each container shows its history with a ↩ Restore button on every past entry. You can roll back to any recorded version, not just the most recent.

Before migrating your stack or rebuilding your Pi, export a backup:

curl http://your-server:5000/api/history/export -o dummy-history.json

Or use the ↓ Export History button in the UI. To restore after:

curl -X POST http://your-server:5000/api/history/import \
  -H "Content-Type: application/json" \
  -d @dummy-history.json

Re-importing is safe — duplicate entries are skipped.

DUMMY auto-detects the registry from the image name:

DUMMY automatically links the changelog for common images. The following are recognised without any configuration:

linuxserver/* · immich-app/immich · gethomepage/homepage · FlareSolverr/FlareSolverr · advplyr/audiobookshelf · AdguardTeam/AdGuardHome · binwiederhier/ntfy · Plex Media Server · qBittorrent · jellyfin/jellyfin · portainer/portainer

Override or add extras using the CHANGELOG_URLS environment variable or the dummy.changelog label.

MIT