Self-host GreptimeDB with Levelrail

A time series database for metrics, logs and traces with SQL, PromQL and OpenTelemetry ingest. This runs a single standalone node with no login on the HTTP port.

  • AuthorGreptimeTeam
  • LicenceApache-2.0
  • Memory512 MiB
  • Services1

How to self-host GreptimeDB

  1. Pull the images

    One image is pulled on your server.

    Show images
    • greptime/greptimedb:v1.3.0
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 4000.

  3. Fill in the secrets

    You do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

GreptimeDB requirements

Memory
About 512 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
4000
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
Apache-2.0, 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 GreptimeDB. 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 GreptimeDB docs page.

Deploy GreptimeDB your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy GreptimeDB from the CLI

levelrail-cli templates deploy greptimedb --name my-greptimedb

Deploy GreptimeDB with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/greptimedb/deploy

GreptimeDB configuration

GreptimeDB services

ServiceImagePortsVolumes
greptimedb greptime/greptimedb:v1.3.0 4000 data -> /greptimedb_data

GreptimeDB environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
4000
Volumes
1 named mount: data -> /greptimedb_data

GreptimeDB FAQ

How much memory does GreptimeDB need?

The catalog lists about 512 MiB of memory for GreptimeDB.

Does GreptimeDB run on arm64?

For GreptimeDB, arm64 support is not confirmed; amd64 is unknown.

What licence is GreptimeDB under?

GreptimeDB is licensed under Apache-2.0, which is permissive, with few conditions on reuse.

Does GreptimeDB need configuration before it starts?

No. The template fills in its own defaults.

Which ports does GreptimeDB use?

GreptimeDB listens on port 4000 inside the stack.

Where does GreptimeDB keep its data?

In a named volume: data mounted at /greptimedb_data.

Can I deploy GreptimeDB 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 GreptimeDB, 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 greptime/greptimedb:v1.3.0 is what you deploy there.

levelrail-cli templates deploy greptimedb --name my-greptimedb