What changed
On September 15, 2026, InfluxData changed the official Docker `influxdb:latest` tag from InfluxDB 2 to InfluxDB 3 Core. InfluxData had pre-announced the change and explicitly warned that users who rely on the floating `latest` tag may receive an unexpected major-version jump the next time Docker pulls the image. Teams that intend to stay on the v2 line are told to pin `influxdb:2` instead. The distinction is important because InfluxDB 3 is not a drop-in rebuild of v2: it uses a new Rust/Apache Arrow/DataFusion/object-storage architecture, supports SQL and InfluxQL rather than Flux, and has separate migration and compatibility guidance for v1/v2 workloads.
Why it matters
A database container tag can be part of an automated restart, server rebuild or deployment pipeline, so a floating tag can change production behavior without a code change in the application repository. The September 15 switch turns that risk into a concrete breaking boundary. Applications that depend on Flux, v2 APIs, storage layout or operational assumptions need an intentional migration plan rather than discovering the difference after a container is replaced. Even teams already planning to adopt v3 should pin exact versions during the migration so the database upgrade is reproducible and reversible.
`latest` now means a different database generation
The Docker Official Image and InfluxData documentation now point `influxdb:latest` to InfluxDB 3 Core. A machine that previously pulled v2 from the same tag can therefore receive v3 during a recreate, image refresh or infrastructure rebuild. Pinning `influxdb:2` preserves the v2 line.
InfluxDB 3 is not a transparent v2 binary replacement
InfluxDB 3 Core is a ground-up implementation using Rust, Apache Arrow, DataFusion and object-storage-oriented persistence. InfluxData provides compatibility endpoints and migration tooling for some v1/v2 workflows, but operators should treat the move as a database migration with schema, API and query-language review rather than as an ordinary container update.
Flux users have a hard compatibility boundary
InfluxDB 3 supports SQL and InfluxQL but does not support Flux as a query language. Applications, dashboards or tasks that still depend on Flux need to stay on v2 or be rewritten before a v3 migration.
Floating tags are especially risky for stateful infrastructure
Using `latest` may be tolerable for a disposable development image, but it is a poor control point for a stateful database. An image digest or explicit version tag lets teams test the exact engine release, coordinate backups and migration steps, and avoid silently changing major versions during routine deployment automation.