Docker: Engine daemon, API and CLI to build and run containers. Signed; SBOM and SLSA v1 provenance.
6.1K
readystack/docker:29.10.0-CE-ubuntu24.04-r1
Source, recipe and records
docker-v29.10.0): https://github.com/moby/moby/tree/06db1734267bf7770914b417bff6556d835bf8ccA cosign-signed build of Docker Engine 29.10.0 (github.com/moby/moby docker-v29.10.0) and Docker CLI 29.10.0 (github.com/docker/cli), with containerd v2.4.2, runc v1.5.3, rootlesskit v3.3.0 and tini 0.19.0, all Apache-2.0 (tini MIT), built clean-room from official upstream source by ReadyStack.
Who: Developers and operations teams who build, ship and run applications in containers.
Why: Docker Engine is the daemon, API and command-line client that build container images and create and manage containers, networks and volumes.
Use case: A team needs a container engine on a shared build host but does not want the daemon running as root. Docker's rootless mode runs the daemon and its containers inside a user namespace as an ordinary user, which limits the damage a vulnerability in the daemon or the container runtime can do.
About the upstream project, written from its own description: https://docs.docker.com/engine/ · https://docs.docker.com/engine/security/rootless/ · https://github.com/docker-library/docs/blob/master/docker/content.md
Signature, user and attestations below were measured on the published digest sha256:cd29030a344949519131881807c48b4a096a2f805e2e3bd251126a2ef80f14e8 on 2026-11-17.
04daa92344a52dbc) on this release's index digest sha256:cd29030a344949519131881807c48b4a096a2f805e2e3bd251126a2ef80f14e8; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/docker:29.10.0-CE-ubuntu24.04-r1.rootless).This image follows the ReadyStack release-tag convention:
The current release is 29.10.0-CE-ubuntu24.04-r1 — 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/docker:29.10.0-CE-ubuntu24.04-r1
# ✗ 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.10.0-CE-ubuntu24.04-r1 (the signature is recorded in the public Sigstore transparency log). Support: [email protected], as set out in the ReadyStack Agreement.
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.10.0-CE-ubuntu24.04-r1
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, localhost, the container's hostname, an IP address, or a name added with DOCKER_TLS_SAN; the container name is not covered, and the default bridge network does not resolve container names, so use a user-defined network and --network-alias docker), DOCKER_TLS_VERIFY=1, DOCKER_CERT_PATH=/certs/client.
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/docker. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:f23435b6069babe28c33610b18a06ed38f4c7193883e57d56a5ad59fbcd7dfa5 on 2026-11-17.
— ReadyStack · readystack.dev
Content type
Image
Digest
sha256:cd29030a3…
Size
97.8 MB
Last updated
2 days ago
docker pull readystack/docker:29.10.0-CE-ubuntu24.04-r1