dankhostself-host anything

Grafana with Docker Compose

Grafana Open Source Software (OSS) enables you to query, visualize, alert on, and explore your metrics, logs, and traces wherever they're stored. In the project's words: Grafana documentation: Grafana OSS introduction checked 2026-09-23

Runs on: amd64, arm64, arm/v7 from each image's registry manifest, checked 2026-09-25; a CPU counts only if every image has a build for it. Image by image

Add Grafana to the builder to use your own domain, get its passwords generated in your browser, and combine it with other apps in one file.

What Grafana needs

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

ResourceMinimumRecommended
RAM512 MBnot stated
Published as "Minimum recommended memory". Some features might need more, and the figure covers the Grafana server only, not the data sources such as Prometheus or Loki that it reads from. Source: Grafana docs: Install Grafana (Hardware recommendations) checked 2026-09-23
CPU1 corenot stated
Published as "Minimum recommended CPU"; some features might need more. Source: Grafana docs: Install Grafana (Hardware recommendations) checked 2026-09-23
DiskThe project publishes no figure

On top of this, Caddy (the reverse proxy in the file) is a single small container.

Which hardware Grafana 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): every image has a build.
ServiceImagePlatforms in the manifestDigestRegistryChecked
grafanagrafana/grafana-enterpriseamd64, arm64, arm/v7sha256:3865fe366013be675e8e80e4b8d7f5828e40b3f132f53cee32d8890d9a0dd27bregistry-1.docker.io2026-09-25

A manifest says an image exists for a CPU, not how well Grafana 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 Grafana 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 Grafana 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: Grafana
# 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"

  # ---- Grafana (grafana.example.org) ----
  # Source: https://grafana.com/docs/grafana/latest/setup-grafana/installation/docker/ (checked 2026-09-23)
  # Source: https://grafana.com/docs/grafana/latest/setup-grafana/configure-grafana/ (checked 2026-09-23)
  # Changed: Removed the documented '3000:3000' port; Caddy reaches grafana:3000 on the proxy network.
  #          GF_SERVER_ROOT_URL (in the docs' example as my.grafana.server over plain HTTP) is your https address; the example's optional GF_PLUGINS_PREINSTALL clock panel is left out.
  #          Added GF_SECURITY_ADMIN_PASSWORD, the environment form (GF_<SECTION>_<KEY>) of the documented [security] admin_password, whose default is 'admin'.
  grafana:
    image: "grafana/grafana-enterprise"
    container_name: "grafana"
    restart: "unless-stopped"
    environment:
      GF_SERVER_ROOT_URL: "https://grafana.example.org/"
      GF_SECURITY_ADMIN_PASSWORD: "${GRAFANA_GF_SECURITY_ADMIN_PASSWORD}"
    volumes:
      - "grafana-storage:/var/lib/grafana"
    networks:
      proxy: {}

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"

volumes:
  caddy-data:
  caddy-config:
  grafana-storage:

Caddyfile save as caddy/Caddyfile

Caddy gets and renews the HTTPS certificate for grafana.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.

# Grafana
grafana.example.org {
	reverse_proxy grafana:3000
}

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

.env

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

# .env for Grafana, from dankhost.com/app/grafana/. Fill the blank secret before starting.
# Keep this file private (chmod 600).

# Grafana
# 24 random letters and digits: the builder fills this in your browser
GRAFANA_GF_SECURITY_ADMIN_PASSWORD=

Changes from the official file

Besides prefixing every service, container, volume, folder and variable with grafana (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 grafana:3000 on the proxy network.
  • GF_SERVER_ROOT_URL (in the docs' example as my.grafana.server over plain HTTP) is your https address; the example's optional GF_PLUGINS_PREINSTALL clock panel is left out.
  • Added GF_SECURITY_ADMIN_PASSWORD, the environment form (GF_<SECTION>_<KEY>) of the documented [security] admin_password, whose default is 'admin'.

Notes for Grafana behind the proxy

  • Log in as 'admin' with GRAFANA_GF_SECURITY_ADMIN_PASSWORD from .env. Grafana sets this password once, on the first run: changing .env later does not change it; use the profile page instead.
  • grafana/grafana-enterprise is the edition the docs call recommended and default; it is free and includes every open-source feature. grafana/grafana is the open-source-only image if you prefer it.
  • Grafana shows data; it does not collect it. Add a data source such as Prometheus, InfluxDB or a database after logging in.

How to run it

  1. At your DNS provider, add an A record named grafana on your domain pointing at the server's public IP address, and forward TCP 80, TCP 443 and UDP 443 to it.
  2. Save the three files in one folder: docker-compose.yml and .env side by side, the Caddyfile at ./caddy/Caddyfile. Replace example.org with your domain in the Caddyfile, the compose file and the .env, or let the builder do it.
  3. Fill the blank GRAFANA_GF_SECURITY_ADMIN_PASSWORD in .env. The builder generates it; on the server, tr -dc A-Za-z0-9 </dev/urandom | head -c 32 prints 32 random letters and digits. Then chmod 600 .env.
  4. Start it:
    docker compose up -d
    docker compose logs -f caddy   # watch the certificate arrive
  5. Open the new address (grafana. plus your domain) in a browser and follow the notes above.

Back it up

Grafana's backup page: copy the SQLite database with Grafana shut down, the plugin folder, and any configuration file you changed. In the official image the database (grafana.db) and plugins live in /var/lib/grafana, the grafana-storage volume; this compose's settings are environment variables in docker-compose.yml.

Below is the BACKUP.md the builder writes next to the compose file above: which of its folders and volumes hold data, 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: Grafana

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)

## Grafana

Grafana's backup page: copy the SQLite database with Grafana shut down, the plugin folder, and any configuration file you changed. In the official image the database (grafana.db) and plugins live in /var/lib/grafana, the grafana-storage volume; this compose's settings are environment variables in docker-compose.yml.

What this compose mounts:
- grafana-storage (named volume, /var/lib/grafana in grafana)
  BACK UP: grafana.db (dashboards, users, data sources, alerts) and installed plugins.

1. Stop grafana. Grafana: 'To ensure data integrity, shut down your Grafana service before backing up the SQLite database.'

    docker compose stop grafana

2. Copy while grafana is stopped:

    docker run --rm --volumes-from grafana -v "$BACKUP":/backup ubuntu tar cvf /backup/grafana-storage.tar /var/lib/grafana

3. Start it again:

    docker compose start grafana

Restore check:

    tar tf "$BACKUP/grafana-storage.tar" > /dev/null && echo OK

Put a copy back (with grafana stopped):

    docker run --rm --volumes-from grafana -v "$BACKUP":/backup ubuntu bash -c "cd /var/lib/grafana && tar xvf /backup/grafana-storage.tar --strip 3"

Stop it, restore the volume with the command above, start it.

Sources:
- Grafana docs: Back up Grafana: https://grafana.com/docs/grafana/latest/administration/back-up-grafana/ (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)

Update it

What docker compose pull does depends only on how each image line in the compose file above is tagged. For Grafana as this page writes it:

ServiceImageHow it is pinnedWhat docker compose pull does
caddycaddy:2Major version only (tag 2)Takes the newest image tagged 2: minor and patch releases of 2, never 3. A new major version needs a tag edit.
grafanagrafana/grafana-enterpriseNot pinned: no tag, which means latestMoves to the newest image published as latest, which can be a new major version.

What Grafana's docs say about updating

Grafana's upgrade guide: upgrade often; because upgrades are backward compatible you can go from any supported release to any other. Back up the database first so you can roll back.

  • Grafana's default database is one SQLite file in /var/lib/grafana; copy it with Grafana stopped for a consistent backup. Keep your settings in environment variables, as this file does, so a new container does not lose them.

Source: Grafana docs: Upgrade Grafana checked 2026-09-30; Grafana docs: Upgrade to Grafana v12.0 (back up the database, Docker) checked 2026-09-30

The steps

  1. Back up first, as in Back it up above. An update can migrate Grafana's data on its first start; the copy is the way back.
  2. Download the new images. Running containers are not touched yet:
    docker compose pull
  3. Recreate the containers whose image changed. Volumes and bind-mounted folders stay as they are:
    docker compose up -d
  4. Watch Grafana start (Ctrl+C stops following the log, not the app):
    docker compose logs -f grafana
  5. Optional: remove the old images the pull left without a tag. This covers every stack on the machine, not only this one:
    docker image prune

Docker's reference for these commands: Docker docs: docker compose pull checked 2026-09-30; Docker docs: docker compose up (recreates changed containers, keeps volumes) checked 2026-09-30; Docker docs: docker image prune checked 2026-09-30

Locked out? Reset the admin password

Sets a new password for Grafana's admin user (user ID 1 unless you name another with --user-id). If the command cannot find the admin user, it lists the admin users and their IDs instead.

Run Grafana's CLI in the container with the new password. Source: Grafana docs: Grafana CLI, Reset admin password read 2026-10-03

docker compose exec grafana grafana cli admin reset-admin-password '<new password>'

Run the commands in the folder that holds docker-compose.yml. Words in angle brackets are placeholders: replace them, brackets included. docker compose exec runs the command in the container that is already running: Docker docs: docker compose exec read 2026-10-03

Sources

Every page below was fetched on the date shown.

Add Grafana to the builder All one hundred apps

Made with AI tools. ยท Privacy