Self-host Grav with Levelrail
A flat-file CMS that stores pages as Markdown files, so there is no database to run. Edit content in the admin panel or directly on the volume.
- Authorgetgrav
- LicenceMIT
- Memory256 MiB
- Services1
How to self-host Grav
-
Pull the images
One image is pulled on your server.
Show images
lscr.io/linuxserver/grav:2.2.21-ls293
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 80.
-
Fill in the secrets
3 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.
After the first start
- Open /admin on the public address and create the first administrator account before anyone else does.
Grav requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Grav. 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 Grav docs page.
Deploy Grav your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Grav from the CLI
levelrail-cli templates install grav --name my-grav Deploy Grav with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/grav/install \
-d '{
"name": "my-grav"
}' Grav configuration
Grav services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| grav | lscr.io/linuxserver/grav:2.2.21-ls293 | 80 | config -> /config |
Grav environment variables
| Variable | Service | Value |
|---|---|---|
| PGID | grav | Preset by the template |
| PUID | grav | Preset by the template |
| TZ | grav | Preset by the template |
Ports and volumes
- Ports
- 80
- Volumes
- 1 named mount: config -> /config
Grav FAQ
How much memory does Grav need?
The catalog lists about 256 MiB of memory for Grav.
Does Grav run on arm64?
For Grav, arm64 support is not confirmed; amd64 is unknown.
What licence is Grav under?
Grav is licensed under MIT, which is permissive, with few conditions on reuse.
Does Grav need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Grav use?
Grav listens on port 80 inside the stack.
Where does Grav keep its data?
In a named volume: config mounted at /config.
Can I deploy Grav 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 Grav, 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 lscr.io/linuxserver/grav:2.2.21-ls293 is what you deploy there.