Self-host Grafana (Postgres) with Levelrail
Grafana backed by Postgres instead of its default embedded SQLite, for multi-instance or external-DB setups.
- Authorgrafana
- LicenceAGPL-3.0-only
- Memory512 MiB
- Archarm64
- Services2
How to self-host Grafana (Postgres)
-
Pull the images
2 images are pulled on your server.
Show images
postgres:16-alpinegrafana/grafana:11.2.0
-
Create the app
2 services start in a single Compose app, with 2 named volume mounts for your data, on port 3000.
-
Fill in the secrets
3 secrets are generated and stored encrypted, 6 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Grafana (Postgres) requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0-only, network copyleft (agpl) license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 3000 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Grafana (Postgres). New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Grafana (Postgres) docs page.
Deploy Grafana (Postgres) your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Grafana (Postgres) from the CLI
levelrail-cli templates deploy grafana-postgres --name my-grafana-postgres Deploy Grafana (Postgres) with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/grafana-postgres/deploy Grafana (Postgres) configuration
Grafana (Postgres) services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:16-alpine | none | grafana_postgres_db_data -> /var/lib/postgresql/data |
| grafana | grafana/grafana:11.2.0 | 3000 | grafana_postgres_data -> /var/lib/grafana |
Grafana (Postgres) environment variables
| Variable | Service | Value |
|---|---|---|
| POSTGRES_DB | db | Preset by the template |
| POSTGRES_PASSWORD | db | Generated at deploy |
| POSTGRES_USER | db | Preset by the template |
| GF_DATABASE_HOST | grafana | Preset by the template |
| GF_DATABASE_NAME | grafana | Preset by the template |
| GF_DATABASE_PASSWORD | grafana | Generated at deploy |
| GF_DATABASE_TYPE | grafana | Preset by the template |
| GF_DATABASE_USER | grafana | Preset by the template |
Show all 9 variables
- GF_SECURITY_ADMIN_PASSWORDgrafanaGenerated at deploy
Ports and volumes
- Ports
- 3000
- Volumes
- 2 named mounts: grafana_postgres_db_data -> /var/lib/postgresql/data, grafana_postgres_data -> /var/lib/grafana
Grafana (Postgres) FAQ
How much memory does Grafana (Postgres) need?
The catalog lists about 512 MiB of memory for Grafana (Postgres) across its 2 services.
Does Grafana (Postgres) run on arm64?
For Grafana (Postgres), an arm64 image is published; amd64 is image published.
What licence is Grafana (Postgres) under?
Grafana (Postgres) is licensed under AGPL-3.0-only, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Grafana (Postgres) need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Grafana (Postgres) bundle?
The template includes Postgres, running as its own service.
Which ports does Grafana (Postgres) use?
Grafana (Postgres) listens on port 3000 inside the stack.
Where does Grafana (Postgres) keep its data?
In named volumes: grafana_postgres_db_data mounted at /var/lib/postgresql/data and grafana_postgres_data mounted at /var/lib/grafana.
Can I deploy Grafana (Postgres) on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Grafana (Postgres), so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, grafana/grafana:11.2.0 is what you deploy there.