Documentation

InfluxDB Enterprise

Install and run InfluxDB v1 Enterprise with Docker

InfluxDB v1 Enterprise provides Docker images for both meta nodes and data nodes to simplify cluster deployment and management. Using Docker allows you to quickly set up and run InfluxDB Enterprise clusters with consistent configurations.

Enterprise license required

You must have a valid license to run InfluxDB Enterprise. Contact sales@influxdata.com for licensing information or obtain a 14-day demo license via the InfluxDB Enterprise portal.

Docker image variants

InfluxDB Enterprise provides two specialized Docker images:

  • influxdb:meta: Enterprise meta node package for clustering
  • influxdb:data: Enterprise data node package for clustering

Requirements

  • Docker installed and running
  • Valid InfluxData license key
  • Network connectivity between nodes
  • At least 3 meta nodes (odd number recommended)
  • At least 2 data nodes

Set up an InfluxDB Enterprise cluster with Docker

  1. Create a Docker network
  2. Start meta nodes
  3. Configure meta nodes to know each other
  4. Start data nodes
  5. Add data nodes to the cluster
  6. Verify the cluster
  7. Stop and restart InfluxDB v1 Enterprise Containers

Create a Docker network

Create a custom Docker network to allow communication between meta and data nodes:

docker network create influxdb

Start meta nodes

Start three meta nodes using the influxdb:meta image. Each meta node requires a unique hostname and the Enterprise license key:

# Start first meta node
docker run -d \
  --name=influxdb-meta-0 \
  --network=influxdb \
  -h influxdb-meta-0 \
  -e INFLUXDB_ENTERPRISE_LICENSE_KEY=your-license-key \
  influxdb:meta

# Start second meta node
docker run -d \
  --name=influxdb-meta-1 \
  --network=influxdb \
  -h influxdb-meta-1 \
  -e INFLUXDB_ENTERPRISE_LICENSE_KEY=your-license-key \
  influxdb:meta

# Start third meta node
docker run -d \
  --name=influxdb-meta-2 \
  --network=influxdb \
  -h influxdb-meta-2 \
  -e INFLUXDB_ENTERPRISE_LICENSE_KEY=your-license-key \
  influxdb:meta

Configure meta nodes to know each other

From the first meta node, add the other meta nodes to the cluster:

# Add the second meta node
docker exec influxdb-meta-0 \
  influxd-ctl add-meta influxdb-meta-1:8091

# Add the third meta node
docker exec influxdb-meta-0 \
  influxd-ctl add-meta influxdb-meta-2:8091

Start data nodes

Start two or more data nodes using the influxdb:data image:

# Start first data node
docker run -d \
  --name=influxdb-data-0 \
  --network=influxdb \
  -h influxdb-data-0 \
  -e INFLUXDB_ENTERPRISE_LICENSE_KEY=your-license-key \
  influxdb:data

# Start second data node
docker run -d \
  --name=influxdb-data-1 \
  --network=influxdb \
  -h influxdb-data-1 \
  -e INFLUXDB_ENTERPRISE_LICENSE_KEY=your-license-key \
  influxdb:data

Add data nodes to the cluster

From the first meta node, register each data node with the cluster:

# Add first data node
docker exec influxdb-meta-0 \
  influxd-ctl add-data influxdb-data-0:8088

# Add second data node
docker exec influxdb-meta-0 \
  influxd-ctl add-data influxdb-data-1:8088

Verify the cluster

Check that all nodes are properly added to the cluster:

docker exec influxdb-meta-0 influxd-ctl show

Expected output:

Data Nodes
==========
ID   TCP Address            Version
4    influxdb-data-0:8088   1.x.x-cX.X.X
5    influxdb-data-1:8088   1.x.x-cX.X.X

Meta Nodes
==========
TCP Address            Version
influxdb-meta-0:8091   1.x.x-cX.X.X
influxdb-meta-1:8091   1.x.x-cX.X.X
influxdb-meta-2:8091   1.x.x-cX.X.X

Configuration options

Using environment variables

You can configure using environment variables with the format INFLUXDB_<SECTION>_<NAME>.

Common environment variables:

  • INFLUXDB_REPORTING_DISABLED=true
  • INFLUXDB_META_DIR=/path/to/metadir
  • INFLUXDB_ENTERPRISE_REGISTRATION_ENABLED=true
  • INFLUXDB_ENTERPRISE_LICENSE_KEY=your-license-key

For all available environment variables, see how to Configure Enterprise.

Using configuration files

You can also mount custom configuration files:

# Mount custom meta configuration
docker run -d \
  --name=influxdb-meta-0 \
  --network=influxdb \
  -h influxdb-meta-0 \
  -v /path/to/influxdb-meta.conf:/etc/influxdb/influxdb-meta.conf \
  -e INFLUXDB_ENTERPRISE_LICENSE_KEY=your-license-key \
  influxdb:meta

# Mount custom data configuration
docker run -d \
  --name=influxdb-data-0 \
  --network=influxdb \
  -h influxdb-data-0 \
  -v /path/to/influxdb.conf:/etc/influxdb/influxdb.conf \
  -e INFLUXDB_ENTERPRISE_LICENSE_KEY=your-license-key \
  influxdb:data

Exposing ports

To access your InfluxDB Enterprise cluster from outside Docker, expose the necessary ports:

# Data node with HTTP API port exposed
docker run -d \
  --name=influxdb-data-0 \
  --network=influxdb \
  -h influxdb-data-0 \
  -p 8086:8086 \
  -e INFLUXDB_ENTERPRISE_LICENSE_KEY=your-license-key \
  influxdb:data

Persistent data storage

To persist data beyond container lifecycles, mount volumes:

# Meta node with persistent storage
docker run -d \
  --name=influxdb-meta-0 \
  --network=influxdb \
  -h influxdb-meta-0 \
  -v influxdb-meta-0-data:/var/lib/influxdb \
  -e INFLUXDB_ENTERPRISE_LICENSE_KEY=your-license-key \
  influxdb:meta

# Data node with persistent storage
docker run -d \
  --name=influxdb-data-0 \
  --network=influxdb \
  -h influxdb-data-0 \
  -v influxdb-data-0-data:/var/lib/influxdb \
  -e INFLUXDB_ENTERPRISE_LICENSE_KEY=your-license-key \
  influxdb:data

Next steps

Once your InfluxDB Enterprise cluster is running:

  1. Set up authentication and authorization for your cluster.
  2. Enable TLS encryption for secure communication.
  3. Install and set up Chronograf for cluster management and visualization.
  4. Configure your load balancer to send client traffic to data nodes. For more information, see Data node installation.
  5. Monitor your cluster for performance and reliability.
  6. Write data with the InfluxDB API.
  7. Query data with the InfluxDB API.

Was this page helpful?

Thank you for your feedback!

© 2025 InfluxData, Inc.

Where are you running InfluxDB?

Customize your InfluxDB Enterprise URL and we’ll update code examples for you.

Default
Custom

For more information, see InfluxDB Enterprise HTTP settings.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2