readystack/pause repository overview

⁠pause

readystack/pause:3.10.2-CE-scratch-r1

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/pause/recipe⁠
• Upstream source at this release's pinned commit (v1.36.6): https://github.com/kubernetes/kubernetes/tree/1b2171b110bb2a2542e1322035c6583ec86eb976⁠
• Product page: https://readystack.dev/products/pause⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/pause⁠
• Release history (JSON): https://readystack.dev/api/releases/pause⁠
• Defect record: https://readystack.dev/defects.html?product=pause⁠
• Today's scan: https://readystack.dev/products/pause#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=pause⁠
• 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 pause 3.10.2 from Kubernetes (github.com/kubernetes/kubernetes build/pause at tag v1.36.6, commit 1b2171b110bb2a2542e1322035c6583ec86eb976), Apache-2.0, compiled from source with gcc 12.2, built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Kubernetes cluster administrators. It is not normally run by hand: the container runtime starts it for every pod.

Why: The pause container is the infrastructure container of a pod. It starts first and keeps the pod's namespaces alive, so the pod's other containers can crash or restart without losing the pod's network setup.

Use case: When a web pod's application container crashes and restarts, the pod keeps its IP address and network configuration, because the pause container still holds them. Administrators meet it mostly in the container runtime's settings, where its image is named as the sandbox image.

About the upstream project, written from its own description: https://github.com/kubernetes/kubernetes/blob/master/build/pause/linux/pause.c⁠ · https://kubernetes.io/docs/concepts/windows/intro/⁠ · https://kubernetes.io/docs/setup/production-environment/container-runtimes/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:205b1d99aed2a00e741d04e7a9dede1ee8eca72e392088e3e2c0d1d0cf649253 on 2026-10-29.

• 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/pause⁠
• ReadyStack release check — passed at release on 2026-10-29: 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:205b1d99aed2a00e741d04e7a9dede1ee8eca72e392088e3e2c0d1d0cf649253; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/pause:3.10.2-CE-scratch-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (65535:65535).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 3.10.2-CE-scratch-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/pause:3.10.2-CE-scratch-r1

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

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/pause:3.10.2-CE-scratch-r1 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Licences

Apache-2.0 AND LGPL-2.1-or-later. /pause is Kubernetes' pause.c (Apache-2.0) linked statically against the GNU C Library 2.36 (LGPL-2.1-or-later): Debian's glibc 2.36-9+deb12u14 (libc6-dev) from the pinned builder image golang:1.26.10-bookworm@sha256:632dff7351799a5a9954a48dc06670ade72ee44e8c351cdc0e5a57af2fea21af. libgcc (GCC 12.2.0, GPL-3.0-or-later WITH GCC-exception-3.1) is linked too; its runtime library exception puts no licence condition on /pause.

This image's org.opencontainers.image.licenses label says only Apache-2.0: it understates the licences, because it does not name glibc. The next revision of this image corrects the label. The image's SPDX document (/usr/local/share/readystack/sbom/pause.spdx.json) lists glibc (libc6-dev 2.36-9+deb12u14) and libgcc (libgcc-12-dev 12.2.0-14+deb12u1).

Corresponding source: glibc, Debian's source package glibc 2.36-9+deb12u14 at https://snapshot.debian.org/package/glibc/2.36-9%2Bdeb12u14/⁠ (glibc_2.36-9+deb12u14.dsc, glibc_2.36.orig.tar.xz, glibc_2.36-9+deb12u14.debian.tar.xz); pause.c, github.com/kubernetes/kubernetes build/pause at v1.36.6. The ReadyStack Hermetic Build Kit for this release carries pause.c and the builder image whose libc.a was linked, so /pause can be rebuilt and relinked offline.

⁠Deployment

Not started by hand: containerd's CRI plugin starts it for every Pod (sandbox_image in /etc/containerd/config.toml). In the Kubernetes VM Stack it is mirrored into the local registry as <LOCAL_REGISTRY>/pause:3.10.2, the name kubeadm v1.36.6 expects (kubeadm config images list).

docker run --rm readystack/pause:3.10.2-CE-scratch-r1 -v

⁠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/products/pause⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:6b74cfa71db2c51e1a21e3342402d3993573ea02a0c85063897eda87958dca26 on 2026-10-29.

— ReadyStack · readystack.dev