readystack/mimir repository overview

⁠Mimir

readystack/mimir:3.2.4-CE-ubuntu24.04-r2

Source, recipe and records

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

A cosign-signed build of mimir, built clean-room from official upstream source, with the source changes listed below by ReadyStack⁠.

⁠Who uses it and why

Who: Platform and SRE teams who need to keep and query metrics from many clusters and teams over long periods.

Why: Grafana Mimir is horizontally scalable, highly available, multi-tenant long-term storage for Prometheus and OpenTelemetry metrics, with queries that aggregate series from many sources into a global view.

Use case: A company runs a Prometheus server in each of its clusters, each keeping only recent data. They all send metrics to Mimir, which keeps them durably in object storage, and engineers query months of history across every cluster at once from one place.

About the upstream project, written from its own description: https://github.com/grafana/mimir⁠ · https://grafana.com/docs/mimir/latest/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:9126a23a1555c034ad7f7b49e51e75782924bf8e7266edf24a5972440fe68070 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/mimir⁠
• ReadyStack release check — passed at release on 2026-11-09: 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:9126a23a1555c034ad7f7b49e51e75782924bf8e7266edf24a5972440fe68070; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/mimir:3.2.4-CE-ubuntu24.04-r2.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (mimir).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 3.2.4-CE-ubuntu24.04-r2 — 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/mimir:3.2.4-CE-ubuntu24.04-r2

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

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

⁠Deployment

See the ReadyStack Hermetic Build Kit for full docs.

docker run -d --name mimir -p 8080:8080 -p 9095:9095 \
  -v mimir-data:/var/mimir \
  readystack/mimir:3.2.4-CE-ubuntu24.04-r2

⁠Source changes (AGPL)

This software is licensed under the GNU Affero General Public License, and the releases below are built from a modified copy of its source. Each line names a release, what ReadyStack changed and where the diff is published. From 2026-10-27 a release's diff carries every upstream file its build changes, the dependency manifests and lockfiles included, so its complete corresponding source is the upstream tag with that diff applied; the diff of an earlier release carries the source edits its line names, and the dependency files that release's build changed are in its release archive (vendored/). If you let users interact with the server over a network, AGPL-3.0 section 13 asks you to offer them its source; for a release from 2026-10-27 on, a link to its diff and the upstream tag does that.

• 3.2.4-CE-ubuntu24.04-r2 — the build raises Go-module dependency versions in go.mod and go.sum where upstream's are older than the fixed, upstream-published releases (security updates; no Mimir source file is edited); full diff of every upstream file the build changes at https://readystack.dev/source/mimir/3.2.4/mimir-3.2.4-readystack.patch⁠
• 3.2.4-CE-ubuntu24.04-r1 — the build raises Go-module dependency versions in go.mod and go.sum where upstream's are older than the fixed, upstream-published releases (security updates; no Mimir source file is edited); full diff of every upstream file the build changes at https://readystack.dev/source/mimir/3.2.4/mimir-3.2.4-readystack.patch⁠
• 3.2.3-CE-ubuntu24.04-r4 — the build raises Go-module dependency versions in go.mod and go.sum where upstream's are older than the fixed, upstream-published releases (security updates; no Mimir source file is edited); full diff of every upstream file the build changes at https://readystack.dev/source/mimir/3.2.3/mimir-3.2.3-readystack.patch⁠
• 3.2.3-CE-ubuntu24.04-r3 — the build raises Go-module dependency versions in go.mod and go.sum where upstream's are older than the fixed, upstream-published releases (security updates; no Mimir source file is edited); full diff of every upstream file the build changes at https://readystack.dev/source/mimir/3.2.3/mimir-3.2.3-readystack.patch⁠

⁠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/mimir⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:15b9b2af9b5fcb7c8d3d42df9bca30053e9843326e2f6013100cc1d949c6184b on 2026-11-09.

— ReadyStack · readystack.dev