Documentation

Initialize an InfluxDB stack

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

InfluxDB automatically creates a new stack each time you apply an InfluxDB template without providing a stack ID. To manually create or initialize a new stack, use the influx stacks init command.

Initialize a stack when applying a template

To automatically create a new stack when applying an InfluxDB template don’t provide a stack ID. InfluxDB applies the resources in the template to a new stack and provides the stack ID the output.

influx apply \
  -o example-org \
  -f path/to/template.yml

Manually initialize a new stack

Use the influx stacks init command to create or initialize a new InfluxDB stack.

Provide the following:

  • Organization name or ID
  • Stack name
  • Stack description
  • InfluxDB template URLs
# Syntax
influx stacks init \
  -o <org-name> \
  -n <stack-name> \
  -d <stack-description \
  -u <package-url>

# Example
influx stacks init \
  -o example-org \
  -n "Example Stack" \
  -d "InfluxDB stack for monitoring some awesome stuff" \
  -u https://example.com/template-1.yml \
  -u https://example.com/template-2.yml

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.7

Key enhancements in InfluxDB 3.7 and the InfluxDB 3 Explorer 1.5.

See the Blog Post

InfluxDB 3.7 is now available for both Core and Enterprise, landing alongside version 1.5 of the InfluxDB 3 Explorer UI. This release focuses on giving developers faster visibility into what their system is doing with one-click monitoring, a streamlined installation pathway, and broader updates that simplify day-to-day operations.

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