Sign inSign up

readystack/tempo

By readystack

•Updated 41 minutes ago

Image
0

705

readystack/tempo repository overview

⁠Tempo

Signed: cosign SBOM: SPDX attached Provenance: SLSA v1

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

A cosign-signed build of tempo, built clean-room from official upstream source by ReadyStack⁠.

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:b240e91daf8aca8e2dfafbf73ea4f362e228ea26321f0e8f2bf8e5362284c19e on 2026-10-27.

  • 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.html#tempo⁠
  • ReadyStack release check — passed at release on 2026-10-27: 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:b240e91daf8aca8e2dfafbf73ea4f362e228ea26321f0e8f2bf8e5362284c19e; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/tempo:v3.1.1-CE-ubuntu24.04-r2.
  • 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-r2 — the release on sale 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.

  • 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-r2

# ✗ 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-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 readystack/tempo:v3.1.1-CE-ubuntu24.04-r2

⁠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 at readystack.dev/buy.html⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:5cbee4bfcb2be7903ebc5fde62e556cb7a4733c3d4b091f2ab2f6ca08893f54f on 2026-10-27.

— ReadyStack · readystack.dev

Tag summary

Content type

Image

Digest

sha256:b240e91da…

Size

94.7 MB

Last updated

41 minutes ago

docker pull readystack/tempo:v3.1.1-CE-ubuntu24.04-r2