readystack/tempo repository overview

⁠Tempo

readystack/tempo:v3.1.1-CE-ubuntu24.04-r3

Source, recipe and records

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

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

⁠Who uses it and why

Who: Teams running many connected services who need distributed tracing to follow requests across them.

Why: Grafana Tempo is a distributed tracing backend that needs only object storage to run. It stores traces from instrumented services, and teams explore them in Grafana to find slow or failing requests.

Use case: Customers report that checkout is sometimes slow, and each checkout request passes through several services. Every service sends traces to Tempo; an engineer opens the slow traces in Grafana, sees which service call took most of the time, and knows where to look.

About the upstream project, written from its own description: https://github.com/grafana/tempo⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:2bc98091eea02036448642bd4917e6f9e0ab76c0ee24d5f490ec5aa73443ce49 on 2026-10-30.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v1, the rubric ce.rodeo published until 2026-10-26) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/tempo⁠
• ReadyStack release check — passed at release on 2026-10-29: 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:2bc98091eea02036448642bd4917e6f9e0ab76c0ee24d5f490ec5aa73443ce49; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/tempo:v3.1.1-CE-ubuntu24.04-r3.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (tempo).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v3.1.1-CE-ubuntu24.04-r3 — 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/tempo:v3.1.1-CE-ubuntu24.04-r3

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

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/tempo:v3.1.1-CE-ubuntu24.04-r3 (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 tempo -p 3200:3200 -p 4317:4317 -p 4318:4318 -v tempo-data:/var/tempo readystack/tempo:v3.1.1-CE-ubuntu24.04-r3

⁠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.

• v3.1.1-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 Tempo source file is edited); full diff of every upstream file the build changes at https://readystack.dev/source/tempo/v3.1.1/tempo-v3.1.1-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/tempo⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:142cf749685cc34b36a1ceb7bb7288f45c4bcf2ae164b6cfcb173875f6113ba7 on 2026-10-29.

— ReadyStack · readystack.dev