maven 3.9.14
Runtime · Build tool · standard · v3.9.14
JDK base image with Apache Maven, used as the build stage for Maven projects; run the resulting jar on jre. Line 3.9.
Version line
The latest line lives at the base page; older lines have their own page so you can pin and verify exactly that version.
Security report (Trivy)
Security report (Trivy) · maven 3.9.14
Published versions
3 tagsEach tag is a multi-arch index (amd64 + arm64) pinned by digest. Tagged by version, never :latest.
Use it as a base image
Reference it in the FROM line of your Dockerfile. Nonroot, read-only root filesystem, built for amd64 and arm64.
FROM ghcr.io/quenchworks/images/maven:3.9.14Or pull it directly
docker pull ghcr.io/quenchworks/images/maven:3.9.14- Version line
- 3.9.14
- Latest line
- 3.9.15, 3.9.14, 3.9.16
- Architectures
- amd64, arm64
- Runs as
- nonroot (uid 1001)
- Root filesystem
- read-only
- License
- Apache-2.0
Verify the supply chain
This image is cosign-signed and carries an SPDX SBOM and a SLSA build-provenance attestation on the same digest. Check all three before you build on it:
# 1. signature — built and signed by QuenchWorks CI
cosign verify ghcr.io/quenchworks/images/maven:3.9.14 \
--certificate-identity-regexp 'https://github.com/quenchworks/.+' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
# 2. SLSA build provenance — which workflow built it, from what
cosign verify-attestation --type https://slsa.dev/provenance/v1 ghcr.io/quenchworks/images/maven:3.9.14 \
--certificate-identity-regexp 'https://github.com/quenchworks/.+' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
# 3. SPDX SBOM — the package inventory
cosign verify-attestation --type https://spdx.dev/Document/v2.3 ghcr.io/quenchworks/images/maven:3.9.14 \
--certificate-identity-regexp 'https://github.com/quenchworks/.+' \
--certificate-oidc-issuer https://token.actions.githubusercontent.comSee the SBOM & provenance guide for reading the SBOM and using these checks in CI.
Best-practice Dockerfile for 3.9.14
Resolve dependencies and package the jar with the maven image (local repository cached under /tmp/.m2), then run it on the slim jre base. The build tool and the dependency cache never ship.
# Build stage: resolve dependencies, then package the jar.FROM ghcr.io/quenchworks/images/maven:3.9.14 AS buildUSER rootWORKDIR /appENV MAVEN_OPTS=-Dmaven.repo.local=/tmp/.m2
COPY pom.xml ./RUN ["mvn", "-B", "-Dmaven.repo.local=/tmp/.m2", "dependency:go-offline"]COPY src ./srcRUN ["mvn", "-B", "-o", "-Dmaven.repo.local=/tmp/.m2", "package", "-DskipTests"]
# Runtime stage: run the jar on the slim JRE base, nonroot.FROM ghcr.io/quenchworks/images/jre:25.0.4 AS runtimeWORKDIR /appCOPY --from=build /app/target/*.jar /app/app.jarUSER 1001EXPOSE 8080ENTRYPOINT ["java", "-Djava.io.tmpdir=/tmp", "-jar", "/app/app.jar"]This Dockerfile is pinned to the 3.9.14 line. For the line-by-line walkthrough and ecosystem variants (npm/Yarn, pip/uv/Poetry, Maven/Gradle), see the Build a Java appguide.
Upstream project: https://maven.apache.org