Self-host InfluxDB with Levelrail

Verified

An open-source time-series database for metrics, events, and IoT analytics.

  • AuthorinfluxdataVerified by Levelrail
  • LicenceApache-2.0
  • Memory512 MiB
  • Archarm64
  • Services1

How to self-host InfluxDB

  1. Pull the images

    One image is pulled on your server.

    Show images
    • influxdb:2.7-alpine
  2. Create the app

    One service starts in a single Compose app, with 2 named volume mounts for your data, on port 8086.

  3. Fill in the secrets

    3 secrets are generated and stored encrypted, 3 settings are preset, 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.

InfluxDB requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 tested
Ports
8086
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
Apache-2.0, permissive license
  • Verified. Verified on arm64 with image tag 2.7-alpine. Our CI ran this exact image version and it answered on its health path. Evidence
  • Host ports. It publishes port 8086 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 InfluxDB. 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 InfluxDB docs page.

Deploy InfluxDB your way

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

Deploy InfluxDB from the CLI

levelrail-cli templates deploy influxdb --name my-influxdb

Deploy InfluxDB 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/influxdb/deploy

InfluxDB configuration

InfluxDB services

ServiceImagePortsVolumes
influxdb influxdb:2.7-alpine 8086 influxdb_data -> /var/lib/influxdb2influxdb_config -> /etc/influxdb2

InfluxDB environment variables

VariableServiceValue
INFLUXDB_INIT_ADMIN_TOKEN influxdb Generated at deploy
INFLUXDB_INIT_BUCKET influxdb Preset by the template
INFLUXDB_INIT_MODE influxdb Preset by the template
INFLUXDB_INIT_ORG influxdb Preset by the template
INFLUXDB_INIT_PASSWORD influxdb Generated at deploy
INFLUXDB_INIT_USERNAME influxdb Generated at deploy

Ports and volumes

Ports
8086
Volumes
2 named mounts: influxdb_data -> /var/lib/influxdb2, influxdb_config -> /etc/influxdb2

InfluxDB FAQ

How much memory does InfluxDB need?

The catalog lists about 512 MiB of memory for InfluxDB.

Does InfluxDB run on arm64?

For InfluxDB, arm64 is tested; amd64 is image published.

What licence is InfluxDB under?

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

Does InfluxDB need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which ports does InfluxDB use?

InfluxDB listens on port 8086 inside the stack.

Where does InfluxDB keep its data?

In named volumes: influxdb_data mounted at /var/lib/influxdb2 and influxdb_config mounted at /etc/influxdb2.

Can I deploy InfluxDB on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id influxdb for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image influxdb:2.7-alpine is what you deploy there.

levelrail-cli templates deploy influxdb --name my-influxdb