readystack/prometheus repository overview

⁠Prometheus

readystack/prometheus:v3.16.0-CE-ubuntu24.04-r2

Source, recipe and records

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

A cosign-signed build of github.com/prometheus/prometheus v3.16.0 (Apache-2.0), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Operations, SRE and platform teams who monitor servers and services and alert on problems.

Why: Prometheus is a monitoring system and time series database. It collects metrics from configured targets at intervals, stores them with labels, evaluates rules written in PromQL, and triggers alerts.

Use case: A team runs web services that expose request counts and latencies. Prometheus discovers the services, collects their metrics at intervals, and fires an alert when the error rate of any service stays above its threshold for several minutes.

About the upstream project, written from its own description: https://github.com/prometheus/prometheus⁠ · https://prometheus.io/docs/introduction/overview/⁠

⁠What you get

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

• 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/prometheus⁠
• 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:b11f684735f6b6a52a9ecd53d2941cb6d7272b4944e5c7ea799c0538a9497910; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/prometheus:v3.16.0-CE-ubuntu24.04-r2.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (nobody).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v3.16.0-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/prometheus:v3.16.0-CE-ubuntu24.04-r2

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

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/prometheus:v3.16.0-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

Single container, single static Go binary, foreground process. Own embedded time-series database (TSDB) on disk; no relational database.

docker run -d --name prometheus -p 9090:9090 -v prom-data:/prometheus readystack/prometheus:v3.16.0-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 a free download for any registered account at readystack.dev/products/prometheus⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:31a617c794e90d43d5a9cd93c8b9406b1dc3dfcc59d7a73e2cda61a618af5cf7 on 2026-11-08.

⁠Trademarks

This image contains Prometheus®.

Prometheus® is a registered trademark of The Linux Foundation.

ReadyStack is not affiliated with or endorsed by The Linux Foundation.

The name identifies the software in this image; it is built from github.com/prometheus/prometheus source at v3.16.0 (commit e2e28adeee2c). ReadyStack does not modify its source.

ReadyStack uses no project logos.

Trademark policy: https://www.linuxfoundation.org/legal/trademark-usage⁠ (read 2026-11-04).

— ReadyStack · readystack.dev