readystack/registry repository overview

⁠Distribution Registry

readystack/registry:v3.1.2-CE-ubuntu24.04-r5

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/registry/recipe⁠
• Upstream source at this release's pinned commit (v3.1.2): https://github.com/distribution/distribution/tree/3220848f15d9279c66a41aa0a257469e6aede1e9⁠
• Product page: https://readystack.dev/products/registry⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/registry⁠
• Release history (JSON): https://readystack.dev/api/releases/registry⁠
• Defect record: https://readystack.dev/defects.html?product=registry⁠
• Today's scan: https://readystack.dev/products/registry#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=registry⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠
• Part of the Kubernetes VM Stack: https://readystack.dev/stacks/kubernetes-vm-stack⁠

A cosign-signed build of github.com/distribution/distribution v3.1.2 (Apache-2.0) - the OCI / Docker Registry HTTP API V2 server, built from ./cmd/registry, built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Teams who want to store and distribute their container images on infrastructure they control.

Why: Distribution Registry is the open-source server that stores container images and other content and serves them using the OCI Distribution Specification.

Use case: A company's build system produces container images that must stay inside its network. It runs Distribution Registry internally: the build pipeline pushes each image there, and every server pulls from it, so image storage and distribution are fully under the company's control.

About the upstream project, written from its own description: https://github.com/distribution/distribution⁠ · https://distribution.github.io/distribution/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:85daf991896e20f5d678a615f5e33275ca9ab64bd055ac73ff35d112e7d7e4a5 on 2026-10-28.

• 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/registry⁠
• ReadyStack release check — passed at release on 2026-10-28: 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:85daf991896e20f5d678a615f5e33275ca9ab64bd055ac73ff35d112e7d7e4a5; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/registry:v3.1.2-CE-ubuntu24.04-r5.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (registry).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v3.1.2-CE-ubuntu24.04-r5 — 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/registry:v3.1.2-CE-ubuntu24.04-r5

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

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/registry:v3.1.2-CE-ubuntu24.04-r5 (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 (registry serve /etc/distribution/config.yml) in the foreground. Stores image layers and manifests on the local filesystem under /var/lib/registry; no database, no web UI, no sidecar.

docker run -d --name registry -p 127.0.0.1:5000:5000 -v registry-data:/var/lib/registry readystack/registry:v3.1.2-CE-ubuntu24.04-r5

Publishes the registry on 127.0.0.1 only, because it speaks plain HTTP until you configure TLS (see Tls in the handbooks). The Docker Engine treats a registry on localhost / 127.0.0.0/8 as allowed over HTTP, so docker login localhost:5000 and docker push localhost:5000/<name>:<tag> work from the same host without TLS; other hosts need TLS (see Tls in the handbooks). On the first start the registry creates its credential file and prints the generated password once in the container log (see Administrator password in the handbooks). The archive ships no Compose file.

⁠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/registry⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:9b7a9955779cf093257a24546a860c35f627315956b12a93b9a03f013dffc449 on 2026-10-28.

— ReadyStack · readystack.dev