readystack/influxdb repository overview

⁠InfluxDB

readystack/influxdb:v3.12.2-CE-ubuntu24.04-r1

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/influxdb/recipe⁠
• Upstream source at this release's pinned commit (v3.12.2): https://github.com/influxdata/influxdb/tree/cc9769917ab399ed5b48567a92b5d34ed4d918ea⁠
• Product page: https://readystack.dev/products/influxdb⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/influxdb⁠
• Release history (JSON): https://readystack.dev/api/releases/influxdb⁠
• Defect record: https://readystack.dev/defects.html?product=influxdb⁠
• Today's scan: https://readystack.dev/products/influxdb#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=influxdb⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠

A cosign-signed build of github.com/influxdata/influxdb v3.12.2 (MIT OR Apache-2.0), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Engineers who collect time-stamped data such as sensor readings, server metrics and network measurements.

Why: InfluxDB is a database built to collect, process and store event and time series data, and to answer queries on recent data quickly for dashboards, monitoring and automation.

Use case: A factory streams readings from its machine sensors every few seconds. InfluxDB ingests them as they arrive, a dashboard queries the latest values with SQL, and a Python plugin running inside the database reacts when a reading crosses a threshold.

About the upstream project, written from its own description: https://github.com/influxdata/influxdb⁠ · https://docs.influxdata.com/influxdb3/core/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:e9a43b81a40c95fbbfc4700d784c9408fadf8bf49d489d88520d55d1f211906a on 2026-11-09.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v2, ce.rodeo's current rubric; scans before 2026-11-08 used cerodeo-v1) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/influxdb⁠
• ReadyStack release check — passed at release on 2026-11-08: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:e9a43b81a40c95fbbfc4700d784c9408fadf8bf49d489d88520d55d1f211906a; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/influxdb:v3.12.2-CE-ubuntu24.04-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (influxdb3).
• Built from source by ReadyStack; the Python UDF runtime (datafusion_udf_wasm_python, an x86_64 ELF) is InfluxData's prebuilt release from github.com/influxdata/datafusion-udf-wasm, downloaded by the vendor stage and checked against the sha256 upstream pins in core/iox_query_udf/build.rs, as upstream's own build does.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v3.12.2-CE-ubuntu24.04-r1 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/influxdb:v3.12.2-CE-ubuntu24.04-r1

# ✗ unsupported (do not pull)
docker pull readystack/influxdb:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/influxdb:v3.12.2-CE-ubuntu24.04-r1 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

Single container running one Rust binary, influxdb3 serve, compiled from the upstream source. A single-node time-series database: it accepts writes in line protocol, answers SQL and InfluxQL queries, and stores its catalog, write-ahead log and Parquet files in a local-disk object store under /var/lib/influxdb3/data (INFLUXDB3_OBJECT_STORE=file; the server also accepts the s3, google and azure object stores, which this release's handbooks do not cover). No external database, no web UI. It runs as the non-root user influxdb3.

docker run -d --name influxdb3 -p 8181:8181 -v influxdb3-data:/var/lib/influxdb3 readystack/influxdb:v3.12.2-CE-ubuntu24.04-r1

On its first start the container creates the operator (admin) token before the server opens port 8181 and keeps it in /var/lib/influxdb3/admin-token.json (mode 600, in the volume). Print it with docker exec influxdb3 readystack-admin-token and send it as Authorization: Bearer <token>. Every request except /health and /api/v1/health needs a token.

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/influxdb⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:968bcc53f2d97e304bacc2cf6cc16dec8a39bb6bc5509bc1fe75c56c4edf2ec0 on 2026-11-09.

— ReadyStack · readystack.dev