readystack/rancher repository overview

⁠Rancher

readystack/rancher:v2.15.3-CE-ubuntu24.04-r1

Source, recipe and records

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

A cosign-signed build of Rancher v2.15.3, built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Organisations that deploy containers in production and run Kubernetes clusters in several places.

Why: Rancher is an open-source container management platform. It provisions and manages Kubernetes clusters from one place, with central authentication, access control and monitoring across all of them.

Use case: A company runs Kubernetes clusters in its own data centre and with a cloud provider. From Rancher, administrators create and upgrade the clusters, apply the same access policies to every team, and see each cluster's health in one view, while developers deploy their applications through its web interface.

About the upstream project, written from its own description: https://github.com/rancher/rancher⁠ · https://ranchermanager.docs.rancher.com/getting-started/overview⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:79cb3e49cd0804c227a2ad46876174623c8b14fe15b8e1480d26cdbcfd48d0d5 on 2026-11-09.

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

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v2.15.3-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/rancher:v2.15.3-CE-ubuntu24.04-r1

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

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

⁠Deployment

SINGLE container, upstream's Docker install: the rancher server process starts an embedded k3s (Kubernetes v1.36.5, server and agent, embedded etcd) and installs its system charts (rancher-webhook, Fleet, system-upgrade-controller, Rancher Turtles, cluster-api) into that local cluster as pods. Unlike upstream's image it runs as the NON-ROOT user rancher (uid 1001): Rancher, k3s and the pods run inside a rootlesskit user namespace (root only inside it; on the host every process is uid 1001 or a subordinate uid 100000-165535), networked through slirp4netns, with ports 80 and 443 forwarded. It still needs docker run --privileged, like upstream's image.

docker run -d --name rancher --restart=unless-stopped --privileged -p 80:80 -p 443:443 -v rancher-data:/var/lib/rancher readystack/rancher:v2.15.3-CE-ubuntu24.04-r1

⁠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/rancher⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:af840225c766507ce7493ed633c4b13abb4af52318e56a874c97ae91d1813ec5 on 2026-11-08.

— ReadyStack · readystack.dev