python
Runtime · Language runtime · standard · v3.14.6
Hardened CPython interpreter with pip, a 0-CVE signed nonroot base image to FROM for Python apps. Ships the latest 3 stable minors (no :latest).
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) · python 3.14.6
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/python:3.14.6Or pull it directly
docker pull ghcr.io/quenchworks/images/python:3.14.6- Version line
- 3.14.6
- Latest line
- 3.13.14, 3.12.13, 3.14.6
- Architectures
- amd64, arm64
- Runs as
- nonroot (uid 1001)
- Root filesystem
- read-only
- License
- PSF-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/python:3.14.6 \
--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/python:3.14.6 \
--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/python:3.14.6 \
--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.14.6
Build a self-contained virtualenv with the full build toolchain in the first stage, then copy just that venv onto a clean python base for the runtime. Compilers and headers never reach the deployed image.
# Build stage: install everything into a venv (build deps included).FROM ghcr.io/quenchworks/images/python:3.14.6 AS buildUSER rootWORKDIR /appENV VIRTUAL_ENV=/opt/venv \ PATH="/opt/venv/bin:$PATH" \ PIP_CACHE_DIR=/tmp/pip
RUN ["python", "-m", "venv", "/opt/venv"]COPY requirements.txt ./RUN ["pip", "install", "--no-cache-dir", "-r", "requirements.txt"]COPY . .
# Runtime stage: copy the venv + app onto a clean python base, run nonroot.FROM ghcr.io/quenchworks/images/python:3.14.6 AS runtimeWORKDIR /appENV VIRTUAL_ENV=/opt/venv \ PATH="/opt/venv/bin:$PATH" \ PYTHONUNBUFFERED=1 \ XDG_CACHE_HOME=/tmpCOPY --from=build /opt/venv /opt/venvCOPY --from=build /app /appUSER 1001EXPOSE 8000CMD ["python", "-m", "app"]This Dockerfile is pinned to the 3.14.6 line. For the line-by-line walkthrough and ecosystem variants (npm/Yarn, pip/uv/Poetry, Maven/Gradle), see the Build a Python appguide.
Upstream project: https://www.python.org