Documentation

Upgrade from InfluxDB 1.x to 2.9 with Docker

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

API token hashing is enabled by default in InfluxDB OSS 2.9.0

Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — capture any plaintext tokens you still need before you upgrade.

For more information, see Token hashing.

Use the automated upgrade process built into the InfluxDB 2.x Docker image to update InfluxDB 1.x Docker deployments to InfluxDB 2.x.

Export continuous queries before upgrading

The automated upgrade process does not migrate InfluxDB 1.x continuous queries (CQs) to InfluxDB 2.x tasks (the 2.x equivalent). Export all of your CQs before upgrading to InfluxDB 2.x. For information about exporting and migrating CQs to tasks, see Migrate continuous queries to tasks.

Upgrade requirements

InfluxDB 2.x provides a 1.x compatibility API, but expects a different storage layout on disk. To account for theses differences, the InfluxDB Docker image migrates 1.x data and into 2.x-compatible data automatically before booting the influxd server.

To ensure InfluxDB reboots post-upgrade without overwriting migrated data, the upgrade won’t run if an existing boltdb file is found at the configured 2.x configuration path.

Find more information about the automated InfluxDB upgrade process, see Automatically upgrade from InfluxDB 1.x to 2.9.

InfluxDB 2.x initialization credentials

The automated InfluxDB upgrade process bootstraps an initial admin user, organization, and bucket required by InfluxDB 2.x. Set the following environment variables in your Docker container to provide setup credentials:

  • DOCKER_INFLUXDB_INIT_USERNAME: Username to set for the admin user (Required).
  • DOCKER_INFLUXDB_INIT_PASSWORD: Password to set for the admin user (Required).
  • DOCKER_INFLUXDB_INIT_ORG: Name to set for the initial organization (Required).
  • DOCKER_INFLUXDB_INIT_BUCKET: Name to set for the initial bucket (Required).
  • DOCKER_INFLUXDB_INIT_RETENTION: Duration for the initial bucket’s retention period. If not set, the initial bucket will retain data forever.
  • DOCKER_INFLUXDB_INIT_ADMIN_TOKEN: API token to associate with the admin user. If not set, InfluxDB automatically generates a token.

File system mounts

The InfluxDB upgrade process requires extra volumes to be mounted into the 2.x container. Use environment variables and Docker mounts to specify and configure the appropriate mount paths for the following:

  • 1.x data on disk
  • Custom 1.x configuration file (if any)
  • 2.x data on disk (/var/lib/influxdb2)
  • 2.x configuration directory (/etc/influxdb2)

The InfluxDB upgrade process searches for mounted 1.x data and configuration files in the following priority order:

  1. 1.x configuration file specified by the DOCKER_INFLUXDB_INIT_UPGRADE_V1_CONFIG environment variable
  2. 1.x data directory specified by the DOCKER_INFLUXDB_INIT_UPGRADE_V1_DIR environment variable
  3. 1.x configuration file mounted at /etc/influxdb/influxdb.conf
  4. 1.x data directory mounted at /var/lib/influxdb

Avoid data loss

By default, the automated upgrade process generates both data and configuration files under /var/lib/influxdb2 and /etc/influxdb2. We recommend mounting volumes at both paths to avoid losing data.

Upgrade initialization mode

Set the DOCKER_INFLUXDB_INIT_MODE environment variable to upgrade.

Minimal upgrade

If you’re currently running a minimal InfluxDB 1.x deployment similar to:

docker run -p 8086:8086 \
  -v influxdb:/var/lib/influxdb \
  influxdb:1.8

To upgrade this minimal deployment to InfluxDB 2.x:

  1. Stop the running InfluxDB 1.x container.

  2. Start the InfluxDB container with the following:

    • Volume mount for the InfluxDB 1.x data directory
    • Volume mount for the InfluxDB 2.x data directory
    • InfluxDB initialization mode environment variable
    • InfluxDB initialization credential environment variables
    • influxdb:2.9 Docker image
    docker run -p 8086:8086 \
      -v influxdb:/var/lib/influxdb \
      -v influxdb2:/var/lib/influxdb2 \
      -e DOCKER_INFLUXDB_INIT_MODE=upgrade \
      -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.9

Upgrade with a custom InfluxDB 1.x configuration file

If you’re currently running an InfluxDB 1.x deployment with a custom configuration file similar to:

docker run -p 8086:8086 \
  -v influxdb:/var/lib/influxdb \
  -v $PWD/influxdb.conf:/etc/influxdb/influxdb.conf:ro \
  influxdb:1.8

To upgrade an InfluxDB 1.x deployment with a custom configuration file to InfluxDB 2.x:

  1. Stop the running InfluxDB 1.x container.

  2. Start the InfluxDB container with the following:

    • Volume mount for the InfluxDB 1.x data directory
    • Volume mount for the InfluxDB 1.x configuration file
    • Volume mount for the InfluxDB 2.x data directory (/var/lib/influxdb2)
    • Volume mount for the InfluxDB 2.x configuration directory (/etc/influxdb2)
    • InfluxDB initialization mode environment variable
    • InfluxDB initialization credential environment variables
    • influxdb:2.9 Docker image
docker run -p 8086:8086 \
  -v influxdb:/var/lib/influxdb \
  -v $PWD/influxdb.conf:/etc/influxdb/influxdb.conf:ro \
  -v influxdb2:/var/lib/influxdb2 \
  -v influxdb2:/etc/influxdb2 \
  -e DOCKER_INFLUXDB_INIT_MODE=upgrade \
  -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.9

Upgrade with custom paths

If you’re currently running an InfluxDB 1.x deployment with the data directory and configuration file mounted at custom paths similar to:

docker run -p 8086:8086 \
  -v influxdb:/root/influxdb/data \
  -v $PWD/influxdb.conf:/root/influxdb/influxdb.conf:ro \
  influxdb:1.8 -config /root/influxdb/influxdb.conf

To upgrade an InfluxDB 1.x deployment with custom paths to InfluxDB 2.x:

  1. Stop the running InfluxDB 1.x container.
  2. Decide to either keep using custom paths or use InfluxDB 2.x default paths.

To retain your custom InfluxDB 1.x paths, start the InfluxDB container with the following:

  • Volume mount for the InfluxDB 1.x data directory
  • Volume mount for the InfluxDB 1.x configuration file
  • Volume mount for the InfluxDB 2.x data directory
  • Volume mount for the InfluxDB 2.x configuration directory
  • InfluxDB initialization mode environment variable
  • InfluxDB initialization credential environment variables
  • InfluxDB 2.x v1 configuration file path environment variable:
    • DOCKER_INFLUXDB_INIT_UPGRADE_V1_CONFIG
  • InfluxDB 1.x custom path environment variables:
    • INFLUXD_CONFIG_PATH
    • INFLUXD_BOLT_PATH
    • INFLUXD_ENGINE_PATH
  • influxdb:<span class="current-version">2.9</span> Docker image
docker run -p 8086:8086 \
  -v influxdb:/root/influxdb/data \
  -v $PWD/influxdb.conf:/root/influxdb/influxdb.conf:ro \
  -v influxdb2:/root/influxdb2/data \
  -v influxdb2:/root/influxdb2 \
  -e DOCKER_INFLUXDB_INIT_MODE=upgrade \
  -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 \
  -e DOCKER_INFLUXDB_INIT_UPGRADE_V1_CONFIG=/root/influxdb/influxdb.conf \
  -e INFLUXD_CONFIG_PATH=/root/influxdb2/config.toml \
  -e INFLUXD_BOLT_PATH=/root/influxdb2/influxdb.bolt \
  -e INFLUXD_ENGINE_PATH=/root/influxdb2/engine \
  influxdb:<span class="current-version">2.9</span>

To use default InfluxDB 2.x paths, start the InfluxDB container with the following:

  • Volume mount for the InfluxDB 1.x data directory
  • Volume mount for the InfluxDB 1.x configuration file
  • Volume mount for the InfluxDB 2.x data directory (/var/lib/influxdb2)
  • Volume mount for the InfluxDB 2.x configuration directory (/etc/influxdb2)
  • InfluxDB initialization mode environment variable
  • InfluxDB initialization credential environment variables
  • InfluxDB 2.x v1 configuration file path environment variable:
    • DOCKER_INFLUXDB_INIT_UPGRADE_V1_CONFIG
  • influxdb:<span class="current-version">2.9</span> Docker image
docker run -p 8086:8086 \
  -v influxdb:/root/influxdb/data \
  -v $PWD/influxdb.conf:/root/influxdb/influxdb.conf:ro \
  -v influxdb2:/var/lib/influxdb2 \
  -v influxdb2:/etc/influxdb2 \
  -e DOCKER_INFLUXDB_INIT_MODE=upgrade \
  -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 \
  -e DOCKER_INFLUXDB_INIT_UPGRADE_V1_CONFIG=/root/influxdb/influxdb.conf \
  influxdb:<span class="current-version">2.9</span>

Use the interactive InfluxQL shell

The InfluxDB 2.9 influx CLI includes an interactive InfluxQL shell for executing InfluxQL queries. The InfluxDB 2.9 Docker image includes the influx CLI.

To start an InfluxQL shell:

  1. Start a bash session in your InfluxDB container:

    docker exec -it influxdb /bin/bash
  2. Set up your influx CLI authentication credentials.

  3. Run the influx v1 shell command.

For more information, see:

To build an interactive shell to execute Flux queries, compile and build a command line Flux REPL from source.


Was this page helpful?

Thank you for your feedback!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 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