HUB
Sign inSign up
jenkins logo

tackleza/jenkins

By tackleza

•Updated 8 days ago

Enhanced Jenkins master with JDK 21, Node.js, Python3, Maven, and pnpm.

Image
Developer tools
0

10K+

tackleza/jenkins repository overview

⁠Jenkins Docker Image

Enhanced Jenkins image with essential development tools pre-installed.

Based on the official jenkins/jenkins⁠ image. Everything from the official image is included, with additional tools added for common development workflows.

⁠Available Tags

TagDescription
latestJenkins on Debian with JDK 25
debian-jdk25Jenkins on Debian with JDK 25
alpine-jdk25Jenkins on Alpine with JDK 25
debian-jdk21Jenkins on Debian with JDK 21
alpine-jdk21Jenkins on Alpine with JDK 21

The latest tag follows the official Jenkins LTS 2.580.2-jdk25 base. Debian and Alpine JDK 21 variants remain available for compatibility. All variants use official upstream Jenkins Java images; no separate JDK is installed.

Use debian-jdk25 for new deployments. Existing controllers still need to be recreated with a fixed image to receive the Jenkins and Java updates.

⁠Included Tools

In addition to the official Jenkins image:

  • JDK — Java Development Kit (version matches tag)
  • Maven (mvn) — Build automation tool
  • Python 3 — Programming language
  • Node.js, npm, pnpm — JavaScript runtime and package managers
  • ping — Basic networking utility

These tools are available immediately in Jenkins pipelines and container shells — no additional setup required.

⁠Quick Start

# Pull the latest image
docker pull tackleza/jenkins:latest

# Run the container
docker run -d \
  --name jenkins \
  -p 8080:8080 \
  -p 50000:50000 \
  tackleza/jenkins:latest

⁠Base Image

This image extends the official jenkins/jenkins⁠ image. For core Jenkins documentation, visit the official image page.

⁠Node.js security baseline (2026-10-23)

All source variants now pin official Node 24.22.1 LTS by digest instead of installing the distribution's nodejs package. The Node project's October 21 security release fixes high-severity Brotli, DNS and TLS vulnerabilities. Node 20 and older, and odd releases 21/23/25, are end of life and receive no further upstream patches. npm is pinned to11.21.1 and pnpm to10.34.7 after auditing the installed package-manager dependency trees. Rebuilding/publishing and recreating dependent controllers is required; changing these Dockerfiles alone does not update existing images or running controllers.

Rebuilding and publishing an image does not update existing controllers; recreate each controller with the fixed image while preserving its home volume and settings.

Sources: official security release⁠, upstream support status⁠.

⁠Bundled package-manager security patch

The images retain npm11.21.1 and pnpm10.34.7. Their bundled ip-address copies are replaced with the exact upstream10.7.4 package to fix GHSA-rxp7-6hxx-x8q5⁠. The Dockerfiles verify the archive SHA256, require both expected package locations and preserve root ownership. The pnpm executable also embeds its own copy: a checksum-guarded backport applies the exact upstream zone-parser fix there, and tests exercise the embedded module independently. This is a reviewed downstream dependency patch; reinstalling either package manager can restore the vulnerable dependency until upstream includes the fix.

Run node tests/ip-address.cjs inside either built image (the script can be supplied on stdin). Validation covers address parsing, IPv6 zone behavior and bounded rejection of the advisory input. Check the actual installed package trees when auditing bundled tooling.

Default-branch pushes and manual GitHub Actions runs always build security source changes. Scheduled runs retain the Jenkins-base digest check. Build scripts stop at the first failed build or push.

The published images record the source revision in org.opencontainers.image.revision. Future npm/pnpm version changes must reassess/remove the downstream patch; its checksum/version guards intentionally fail if the expected bundle changes. Build a variant from the repository root with docker build -f latest/Dockerfile ., or run its existing build.sh from the variant directory.

⁠Embedded UUID buffer bounds

The pnpm bundle also contains uuid9.0.1 code affected by GHSA-w5hq-g745-h8pq⁠. The same guarded patch script backports upstream's bounds check to the embedded v3/v5 buffer writer; uuid9 does not implement v6. Tests load the actual bundled functions and verify canonical vectors, valid output buffers and rejection before partial writes for undersized/negative/overflow bounds. This avoids changing the shared pnpm major. Version-based scanners can still identify uuid9.0.1; record this source backport and its regression tests rather than treating the bundle as an unmodified vulnerable release.

Tag summary

Content type

Image

Digest

sha256:c47256a71…

Size

466.6 MB

Last updated

8 days ago

docker pull tackleza/jenkins