readystack/jenkins repository overview

⁠Jenkins

readystack/jenkins:2.580.1-CE-ubuntu24.04-r3

A cosign-signed build of github.com/jenkinsci/jenkins jenkins-2.580.1 (MIT; bundled Winstone is LGPL/CDDL, CDDL elected; the 63 bundled plugins are upstream's prebuilt releases, unmodified), built clean-room from official upstream source by ReadyStack⁠.

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:a7cdd71687c491f9f212ca4085a871b50b81c96b62284892e2eb1e3c5f659e6a on 2026-10-21.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with ce.rodeo's published rubric) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products.html#jenkins⁠
• ReadyStack release check — passed at release on 2026-10-21: 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:a7cdd71687c491f9f212ca4085a871b50b81c96b62284892e2eb1e3c5f659e6a; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/jenkins:2.580.1-CE-ubuntu24.04-r3.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (jenkins).
• Built from source by ReadyStack; the 63 bundled plugins are upstream's prebuilt releases, unmodified.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 2.580.1-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.

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

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

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

Single container running jenkins.war on its embedded Winstone/Jetty container, with state under JENKINS_HOME. No external database.

Secrets go in an env file that only you can read, not on the command line, and passwords that only set up the first start come out of it after setup. Create jenkins.env with install -m 600 /dev/null jenkins.env, then write these lines into it with an editor, with your own values (a value typed into a shell stays in its history). Docker reads each line as written: no quotes around a value, no spaces around =.

# First start only: the first start of an empty JENKINS_HOME creates the administrator (JENKINS_ADMIN_USER, default admin) with JENKINS_ADMIN_PASSWORD. Remove this line after setup and recreate the container; the administrator keeps the password.
JENKINS_ADMIN_PASSWORD=YOUR_ADMIN_PASSWORD

docker run -d --name jenkins -p 8080:8080 --env-file ./jenkins.env -v jenkins-home:/var/jenkins_home readystack/jenkins:2.580.1-CE-ubuntu24.04-r3

Sign in at http://localhost:8080⁠ as admin with the password from jenkins.env. Once the first start has created the administrator, remove the JENKINS_ADMIN_PASSWORD line from jenkins.env and recreate the container on the same volume (docker rm -f jenkins, then the docker run command again): the entrypoint needs the variable only while JENKINS_HOME has no security realm, so Jenkins starts, the administrator keeps the password, and the password is no longer in the container's environment (tested).

⁠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:557f2aa474a26921ad32da5907a15dedad4184b07743dbe2d829ccb3be7c0c1e on 2026-10-21.

— ReadyStack · readystack.dev