Umami with Docker Compose

What Umami needs

Only figures Umami's own documentation publishes, each linked to the page it is on. Where the project gives no number, this page does not invent one.

On top of this, Caddy (the reverse proxy in the file) is a single small container. Umami itself runs as 2 containers: umami, umami-db.

Which hardware Umami has images for

Read from each image's manifest list in its registry (anonymous, read-only) when this page was built. An app counts for a CPU only if every one of its images lists it.

• x86-64 PC or NAS (linux/amd64): every image has a build.
• Raspberry Pi 4/5, 64-bit OS (linux/arm64): every image has a build.
• Raspberry Pi 3 or Zero 2 W, 32-bit OS (linux/arm/v7): no image for umami. No image for this hardware; the builder leaves the app out.

A manifest says an image exists for a CPU, not how well Umami runs on it: a build for arm64 or arm/v7 can still be too slow or need more memory than the board has. The RAM and disk Umami publishes are in the table above and, for a whole set of apps against a Raspberry Pi, on Will it run on my machine?. A tag like latest can move to a new digest after the date checked.

docker-compose.yml

This is exactly what the builder writes for Umami alone on example.org: the official definition with its published ports removed and Caddy added in front. Every ${VARIABLE} is defined in the .env below.

# docker-compose.yml built at dankhost.com for: Umami
# Each app block is its official compose definition. Only the names were prefixed with
# the app slug (services, containers, volumes, bind folders, .env variables) so any set of
# apps can share one file; other differences are listed under "Changed:" in each block.
# Only Caddy publishes ports. Secrets live in .env next to this file.

services:
  # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ----
  # Source: https://caddyserver.com/docs/running (checked 2026-09-23)
  # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23)
  # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly.
  caddy:
    image: "caddy:2"
    container_name: "caddy"
    restart: "unless-stopped"
    ports:
      - "80:80"
      - "443:443"
      - "443:443/udp"
    volumes:
      - "./caddy:/etc/caddy"
      - "caddy-data:/data"
      - "caddy-config:/config"
    networks:
      proxy:
        ipv4_address: "172.30.0.2"

  # ---- Umami (umami.example.org) ----
  # Source: https://github.com/umami-software/umami/blob/master/docker-compose.yml (checked 2026-09-29)
  # Source: https://umami.is/docs/login (checked 2026-09-29)
  # Source: https://umami.is/docs/environment-variables (checked 2026-09-29)
  # Changed: Removed the documented '3000:3000' port; Caddy reaches umami:3000 on the proxy network. The database stays on Umami's own network with no internet access.
  #          The database password 'umami' is replaced by a generated one, used both in DATABASE_URL and as POSTGRES_PASSWORD. APP_SECRET ('replace-me-with-a-random-string') is 64 random letters and digits, and TWO_FACTOR_ENCRYPTION_KEY is a random 64-character hex string, the form the file asks for (openssl rand -hex 32).
  #          The database healthcheck names the user and database (umami) directly instead of the file's $${POSTGRES_USER} and $${POSTGRES_DB}, which hold the same values.
  umami:
    image: "ghcr.io/umami-software/umami:latest"
    container_name: "umami"
    environment:
      DATABASE_URL: "postgresql://umami:${UMAMI_DB_PASSWORD}@db:5432/umami"
      APP_SECRET: "${UMAMI_APP_SECRET}"
      TWO_FACTOR_ENCRYPTION_KEY: "${UMAMI_TWO_FACTOR_ENCRYPTION_KEY}"
    depends_on:
      umami-db:
        condition: "service_healthy"
    init: true
    restart: "always"
    healthcheck:
      test:
        - "CMD-SHELL"
        - "curl http://localhost:3000/api/heartbeat"
      interval: "5s"
      timeout: "5s"
      retries: 5
    networks:
      proxy: {}
      umami-backend: {}
  umami-db:
    image: "postgres:15-alpine"
    container_name: "umami-db"
    environment:
      POSTGRES_DB: "umami"
      POSTGRES_USER: "umami"
      POSTGRES_PASSWORD: "${UMAMI_DB_PASSWORD}"
    volumes:
      - "umami-db-data:/var/lib/postgresql/data"
    restart: "always"
    healthcheck:
      test:
        - "CMD-SHELL"
        - "pg_isready -U umami -d umami"
      interval: "5s"
      timeout: "5s"
      retries: 5
    networks:
      umami-backend:
        aliases:
          - "db"

networks:
  # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact.
  # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's
  # ipv4_address and in every trusted-proxy value to a free 172.x.0 range.
  proxy:
    ipam:
      config:
        - subnet: "172.30.0.0/24"
          ip_range: "172.30.0.128/25"
          gateway: "172.30.0.1"
  umami-backend:
    internal: true

volumes:
  caddy-data:
  caddy-config:
  umami-db-data:

Caddyfile save as caddy/Caddyfile

Caddy gets and renews the HTTPS certificate for umami.example.org by itself once the DNS record points at your server and ports 80 and 443 reach it.

# Caddyfile built at dankhost.com. Save it as ./caddy/Caddyfile next to docker-compose.yml.
# Caddy gets and renews a Let's Encrypt certificate for each name below by itself,
# once the DNS records point at this server and ports 80 and 443 reach it.

# Umami
umami.example.org {
	reverse_proxy umami:3000
}

Already running nginx, Nginx Proxy Manager, Caddy or Traefik? The reverse-proxy settings Umami needs, for all four, each cited to Umami's own docs.

.env

The secrets are left blank here on purpose: a password printed on a public page is the same for everyone who copies it. The builder fills them with random letters and digits made in your browser.

# .env for Umami, from dankhost.com/app/umami/. Fill the blank secrets before starting.
# Keep this file private (chmod 600).

# Umami
# 32 random letters and digits: the builder fills this in your browser
UMAMI_DB_PASSWORD=
# 64 random letters and digits: the builder fills this in your browser
UMAMI_APP_SECRET=
# 64 random letters and digits: the builder fills this in your browser
UMAMI_TWO_FACTOR_ENCRYPTION_KEY=

Changes from the official file

Besides prefixing every service, container, volume, folder and variable with umami (so any set of apps can share one file), these are all the differences from what the project documents:

• Removed the documented '3000:3000' port; Caddy reaches umami:3000 on the proxy network. The database stays on Umami's own network with no internet access.
• The database password 'umami' is replaced by a generated one, used both in DATABASE_URL and as POSTGRES_PASSWORD. APP_SECRET ('replace-me-with-a-random-string') is 64 random letters and digits, and TWO_FACTOR_ENCRYPTION_KEY is a random 64-character hex string, the form the file asks for (openssl rand -hex 32).
• The database healthcheck names the user and database (umami) directly instead of the file's $${POSTGRES_USER} and $${POSTGRES_DB}, which hold the same values.

Notes for Umami behind the proxy

• Log in at https://umami.example.org as admin with the password umami, the default account the docs describe, and change that password at once (Settings > Profile): until you do, anyone who finds the address can log in.
• Then add a website in Settings > Websites and put the tracking code it shows into your site's pages.
• The repository's compose file uses the image tag 'latest'.

Back it up

Umami publishes no backup procedure. Everything it records is in its PostgreSQL database, so the plan below is a pg_dump, the method PostgreSQL documents.

Below is the BACKUP.md the builder writes next to the compose file above: which of its folders and volumes hold data, the dump command the project documents, rewritten for this file's service names, what to copy with which container stopped, and a restore check. Pick more apps in the builder and it covers them all in one file.

# BACKUP.md built at dankhost.com for: Umami

What to copy from the docker-compose.yml built with this file, the database dump each project documents (rewritten for the service names in that file), what to copy with which container stopped, and how to check the result. Run every command in the folder that holds docker-compose.yml.

The folders are owned by the containers' users: put sudo in front of tar if it says "Permission denied". Named volumes live under /var/lib/docker/volumes, not next to the compose file, so they are copied through a throwaway ubuntu container (Docker's documented --volumes-from method). tar makes a full copy each run; for large folders an incremental tool (restic, borg, rsync) saves time and space.

Never run "docker compose down -v" on this file: it deletes the named volumes of every app in it.

## Before you start

    BACKUP=/mnt/backup/selfhost   # change this: a disk or machine other than this server's system disk
    mkdir -p "$BACKUP"

## Every time: the three stack files

    tar czf "$BACKUP/stack-files.tar.gz" docker-compose.yml .env caddy

.env holds the database passwords and secret keys the apps were set up with; keep this archive as private as the data.

## Caddy (the reverse proxy)

Caddy's docs: 'The data directory must not be treated as a cache.' It holds the TLS certificates and their private keys; without it Caddy has to ask Let's Encrypt for every certificate again.

- caddy-data (named volume, /data in caddy)
  BACK UP: TLS certificates, private keys, OCSP staples.
- caddy-config (named volume, /config in caddy)
  SKIP: the last active configuration, kept for 'caddy run --resume', which this setup does not use: it starts from the Caddyfile.
- ./caddy (/etc/caddy in caddy)
  IN stack-files.tar.gz: the Caddyfile, copied with the stack files above.

Copy (Caddy keeps serving while you copy):

    docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu tar cvf /backup/caddy-data.tar /data

Restore check:

    tar tf "$BACKUP/caddy-data.tar" > /dev/null && echo OK
    docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu bash -c "cd /data && tar xvf /backup/caddy-data.tar --strip 1"

Sources:
- Caddy docs: Conventions, Data directory: https://caddyserver.com/docs/conventions#data-directory (checked 2026-09-24)
- Docker docs: Volumes, Back up, restore, or migrate data volumes: https://docs.docker.com/engine/storage/volumes/#back-up-restore-or-migrate-data-volumes (checked 2026-09-24)

## Umami

Umami publishes no backup procedure. Everything it records is in its PostgreSQL database, so the plan below is a pg_dump, the method PostgreSQL documents.

What this compose mounts:
- umami-db-data (named volume, /var/lib/postgresql/data in umami-db)
  COVERED BY THE COMMAND BELOW: Postgres data files; copy them only with the database stopped.

1. Database dump for umami-db:

    docker compose exec -T umami-db pg_dump -U umami umami > "$BACKUP/umami.dump"

   POSTGRES_USER and POSTGRES_DB are both umami in this compose; the redirect writes the dump on the host.

2. Nothing else to copy: the command above holds all of Umami's data. pg_dump is consistent while Umami runs: the dump is a snapshot of the database at the moment it started (PostgreSQL docs).

Restore check:

    grep -c 'PostgreSQL database dump complete' "$BACKUP/umami.dump"   # 1 means pg_dump finished

Load it into an empty database. On a new server start only the database first, then Umami:

    docker compose up -d umami-db
    docker compose exec -T umami-db psql -U umami umami < "$BACKUP/umami.dump"
    docker compose up -d

Sources:
- Umami repository: docker-compose.yml (Umami with a PostgreSQL database): https://github.com/umami-software/umami/blob/master/docker-compose.yml (checked 2026-09-29)
- PostgreSQL docs: SQL Dump: https://www.postgresql.org/docs/current/backup-dump.html (checked 2026-09-29)

Sources

Every page below was fetched on the date shown.

• Umami README on GitHub checked 2026-09-29 (what it does)
• Umami repository: docker-compose.yml (Umami with a PostgreSQL database) checked 2026-09-29 (compose definition and proxy settings, backup plan)
• Umami docs: Login (default account admin / umami) checked 2026-09-29 (compose definition and proxy settings)
• Umami docs: Environment variables (APP_SECRET, DATABASE_URL) checked 2026-09-29 (compose definition and proxy settings)
• Caddy docs: Keep Caddy running (Docker Compose section) checked 2026-09-23 (Caddy)
• Vaultwarden wiki: Caddy with HTTP challenge (uses the caddy:2 image) checked 2026-09-23 (Caddy)
• PostgreSQL docs: SQL Dump checked 2026-09-29 (backup plan)
• Caddy docs: Conventions, Data directory checked 2026-09-24 (backup plan)
• Docker docs: Volumes, Back up, restore, or migrate data volumes checked 2026-09-24 (backup plan)

Add Umami to the builder All fifty apps