readystack/docker repository overview

⁠Docker

readystack/docker:29.9.2-CE-ubuntu24.04-r3

A cosign-signed build of Docker Engine 29.9.2 (github.com/moby/moby docker-v29.9.2) and Docker CLI 29.9.2 (github.com/docker/cli), with containerd v2.4.2, runc v1.5.2, rootlesskit v3.3.0 and tini 0.19.0, all Apache-2.0 (tini MIT), built clean-room from official upstream source by ReadyStack⁠.

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:424c96e74a1551f8f380e48fd02b3dfa0c129b693a866549f5eb0ac9cdddf9b6 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.html#docker⁠
• 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:424c96e74a1551f8f380e48fd02b3dfa0c129b693a866549f5eb0ac9cdddf9b6; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/docker:29.9.2-CE-ubuntu24.04-r3.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (rootless).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 29.9.2-CE-ubuntu24.04-r3 — 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.

• 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/docker:29.9.2-CE-ubuntu24.04-r3

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

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

One container that is a Docker host: dockerd, containerd and runc run as the non-root user rootless (uid 1000) inside a rootlesskit user namespace (root inside it is uid 1000 outside, the other ids are the subordinate ids 100000-165535), with slirp4netns for networking. The container needs --privileged, as docker-library's docker:dind-rootless does. Inner containers, images and volumes live under /home/rootless/.local/share/docker (the image's volume). The docker CLI is in the image; clients elsewhere connect over TLS on port 2376.

docker run -d --name dind --privileged -p 2376:2376 -v dind-data:/home/rootless/.local/share/docker -v dind-certs:/certs readystack/docker:29.9.2-CE-ubuntu24.04-r3

Then docker exec dind docker info, or from the host: copy the client certificate out (docker cp dind:/certs/client ./dind-client) and run docker --host tcp://127.0.0.1:2376 --tlsverify --tlscacert ./dind-client/ca.pem --tlscert ./dind-client/cert.pem --tlskey ./dind-client/key.pem info. In CI (GitLab services, for example) share /certs/client with the job container and set DOCKER_HOST=tcp://:2376 (the name must be one the server certificate covers: docker, the hostname, an IP address, or a name added with DOCKER_TLS_SAN), DOCKER_TLS_VERIFY=1, DOCKER_CERT_PATH=/certs/client.

⁠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:f97b1b29d0c0da6df421b790650defe2e2f890540092bc44def0d166398d429b on 2026-10-28.

— ReadyStack · readystack.dev