Quick reference

• Maintained by:

[InfluxData](https://github.com/influxdata/influxdata-docker)

• Where to get help:

[InfluxDB Discord Server](https://discord.gg/9zaNCW2PRT) *(preferred for **InfluxDB 3 Core**, **InfluxDB 3 Enterprise**)*, [InfluxDB Community Slack](https://influxdata.com/slack) *(preferred for **InfluxDB v2**, **v1**)\*

Supported tags and respective Dockerfile links

• 1.12, 1.12.4

• 1.12-alpine, 1.12.4-alpine

• 1.12-data, 1.12.4-data, data

• 1.12-data-alpine, 1.12.4-data-alpine, data-alpine

• 1.12-meta, 1.12.4-meta, meta

• 1.12-meta-alpine, 1.12.4-meta-alpine, meta-alpine

• 1.11, 1.11.8

• 1.11-alpine, 1.11.8-alpine

• 1.11-data, 1.11.9-data

• 1.11-data-alpine, 1.11.9-data-alpine

• 1.11-meta, 1.11.9-meta

• 1.11-meta-alpine, 1.11.9-meta-alpine

• 2.8, 2.8.0

• 2.8-alpine, 2.8.0-alpine

• 2, 2.9, 2.9.1, latest

• 2-alpine, 2.9-alpine, 2.9.1-alpine, alpine

• 3.9-core, 3.9.11-core

• 3.9-enterprise, 3.9.11-enterprise

• 3.10-core, 3.10.5-core

• 3.10-enterprise, 3.10.5-enterprise

• 3-core, 3.11-core, 3.11.1-core, core

• 3-enterprise, 3.11-enterprise, 3.11.1-enterprise, enterprise

Quick reference (cont.)

• Where to file issues:

[https://github.com/influxdata/influxdata-docker/issues](https://github.com/influxdata/influxdata-docker/issues?q=)

• Supported architectures: (more info)

[`amd64`](https://hub.docker.com/r/amd64/influxdb/), [`arm64v8`](https://hub.docker.com/r/arm64v8/influxdb/)

• Published image artifact details:

[repo-info repo's `repos/influxdb/` directory](https://github.com/docker-library/repo-info/blob/master/repos/influxdb) ([history](https://github.com/docker-library/repo-info/commits/master/repos/influxdb))  
(image metadata, transfer size, etc)

• Image updates:

[official-images repo's `library/influxdb` label](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Finfluxdb)  
[official-images repo's `library/influxdb` file](https://github.com/docker-library/official-images/blob/master/library/influxdb) ([history](https://github.com/docker-library/official-images/commits/master/library/influxdb))

• Source of this description:

[docs repo's `influxdb/` directory](https://github.com/docker-library/docs/tree/master/influxdb) ([history](https://github.com/docker-library/docs/commits/master/influxdb))

Notice

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

What is InfluxDB?

InfluxDB is the time series database platform designed to collect, store, and process large amounts of event and time series data. Ideal for monitoring (sensors, servers, applications, networks), financial analytics, and behavioral tracking.

Start InfluxDB 3 Core

... via docker compose
Example compose.yaml for influxdb:

# compose.yaml
name: influxdb3
services:
  influxdb3-core:
    container_name: influxdb3-core
    image: influxdb:3-core
    ports:
      - 8181:8181
    command:
      - influxdb3
      - serve
      - --node-id=node0
      - --object-store=file
      - --data-dir=/var/lib/influxdb3/data
      - --plugin-dir=/var/lib/influxdb3/plugins
    volumes:
      - type: bind
        source: ~/.influxdb3/core/data
        target: /var/lib/influxdb3/data
      - type: bind
        source: ~/.influxdb3/core/plugins
        target: /var/lib/influxdb3/plugins

Alternatively, you can use the following command to start InfluxDB 3 Core:

docker run --rm -p 8181:8181 \
  -v $PWD/data:/var/lib/influxdb3/data \
  -v $PWD/plugins:/var/lib/influxdb3/plugins \
  influxdb:3-core influxdb3 serve \
    --node-id=my-node-0 \
    --object-store=file \
    --data-dir=/var/lib/influxdb3/data \
    --plugin-dir=/var/lib/influxdb3/plugins

InfluxDB 3 Core starts with:

• Data persistence at /var/lib/influxdb3/data
• Python processing engine enabled with plugin directory
• HTTP API listening on port 8181

Using InfluxDB 3 Core

After starting your InfluxDB 3 server, follow the Get Started guide to create an authorization token and start writing, querying, and processing data via the built-in influxdb3 CLI or the HTTP API.

Recommended tools for InfluxDB 3 Core

Use the following tools with InfluxDB 3 Core:

• InfluxDB 3 Explorer UI: Visualize, query, and manage your data with the standalone web interface designed for InfluxDB 3. View on Docker Hub
• Telegraf: Collect, transform, and send metrics from hundreds of sources directly to InfluxDB 3. View on Docker Hub
• Official Client Libraries: Integrate InfluxDB 3 into your applications using supported libraries for Python, Go, JavaScript, and more.

Customize server options

Customize your instance with available server options:

docker run --rm influxdb:3-core influxdb3 serve --help

Available InfluxDB variants

• influxdb:3-core - Latest InfluxDB OSS (InfluxDB 3 Core)
• influxdb:2 - Previous generation OSS (InfluxDB v2)
• influxdb:1.11 - InfluxDB v1

InfluxDB 3 Core (influxdb:3-core) - Latest OSS

• Latest generation using object storage with the InfluxDB 3 storage engine, Apache Arrow, and DataFusion SQL
• Sub-10ms queries and unlimited cardinality
• Supports SQL and InfluxQL queries
• Includes Python processing engine
• Designed for real-time monitoring and recent data
• Includes InfluxDB v1 and v2 compatibility APIs

InfluxDB v2 (influxdb:2)

• Built on the TSM storage engine
• Supports Flux query language
• Integrated UI and dashboards
• Includes v1 compatibility API that supports InfluxQL

InfluxDB v1 (influxdb:1.11)

• Built on the TSM storage engine
• Original version with InfluxQL query language
• Proven stability for existing deployments

InfluxDB 3 Enterprise (license required) (influxdb:3-enterprise)

Adds unlimited data retention, compaction, clustering, and high availability to InfluxDB 3 Core.
For setup instructions, see the InfluxDB 3 Enterprise installation documentation.

InfluxDB v1 Enterprise (license required)

• influxdb:1.11-data - Data nodes for clustering
• influxdb:1.11-meta - Meta nodes for cluster coordination (port 8091)

For setup instructions, see the InfluxDB v1 Enterprise Docker documentation.

Version compatibility

Migration paths

To migrate from v1 or v2 to InfluxDB 3:

1. Dual-write new data to v1/v2 and InfluxDB 3.
2. Query historical data from v1/v2 and write it to InfluxDB 3. InfluxDB 3 Enterprise is recommended for historical query capability.

Using InfluxDB v2

InfluxDB v2 is a previous version. Consider InfluxDB 3 Core for new deployments.
Enter the following command to start InfluxDB v2 initialized with custom configuration:

docker run -d -p 8086:8086 \
  -v $PWD/data:/var/lib/influxdb2 \
  -v $PWD/config:/etc/influxdb2 \
  -e DOCKER_INFLUXDB_INIT_MODE=setup \
  -e DOCKER_INFLUXDB_INIT_USERNAME=my-user \
  -e DOCKER_INFLUXDB_INIT_PASSWORD=my-password \
  -e DOCKER_INFLUXDB_INIT_ORG=my-org \
  -e DOCKER_INFLUXDB_INIT_BUCKET=my-bucket \
  influxdb:2

After the container starts, visit http://localhost:8086 to view the UI.
For detailed instructions, see the InfluxDB v2 Docker Compose documentation.

Using InfluxDB v1

InfluxDB v1 is a previous version. Consider InfluxDB 3 Core for new deployments.

docker run -d -p 8086:8086 \
  -v $PWD:/var/lib/influxdb \
  influxdb:1.11

This starts InfluxDB v1 with:

• HTTP API on port 8086
• Data persisted to current directory

For more information, see the InfluxDB v1 Docker documentation. For v1 Enterprise installation, see the InfluxDB Enterprise v1 documentation.

Image Variants

The influxdb images come in many flavors, each designed for a specific use case.

influxdb:<version>

This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.

influxdb:<version>-alpine

This image is based on the popular Alpine Linux project, available in the alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is useful when final image size being as small as possible is your primary concern. The main caveat to note is that it does use musl libc instead of glibc and friends, so software will often run into issues depending on the depth of their libc requirements/assumptions. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
To minimize image size, it's uncommon for additional related tools (such as git or bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the alpine image description for examples of how to install packages if you are unfamiliar).

License

View license information for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the repo-info repository's influxdb/ directory.
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.