uv
Runtime · Build tool · standard · v0.13.9
Python base image with uv, a fast Rust-based installer and resolver, used as the build stage for Python projects. Line 0.11.
Security report (Trivy)
Security report (Trivy) · uv 0.13.9
Published versions
1 tagEach tag is a multi-arch index (amd64 + arm64) pinned by digest. Tagged by version, never :latest.
| Version | Size | Published | Digest |
|---|---|---|---|
| 0.13.9latest | 43.3 MB | 2026-11-17 | sha256:663d0afe2965… |
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/uv:0.13.9Or pull it directly
docker pull ghcr.io/quenchworks/images/uv:0.13.9- Version line
- 0.13.9
- Latest line
- 0.13.9
- Architectures
- amd64, arm64
- Runs as
- nonroot (uid 1001)
- Root filesystem
- read-only
- License
- MIT OR 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/uv:0.13.9 \
--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/uv:0.13.9 \
--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/uv:0.13.9 \
--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 0.13.9
uv leads: it resolves and syncs the locked, production-only dependency set into a venv, then a clean python base receives that venv and the app. uv never ships in the runtime image.
# Build stage: uv resolves and installs into a project venv, fast.FROM ghcr.io/quenchworks/images/uv:0.13.9 AS buildUSER rootWORKDIR /appENV UV_PROJECT_ENVIRONMENT=/opt/venv \ UV_COMPILE_BYTECODE=1 \ UV_CACHE_DIR=/tmp/uv
COPY pyproject.toml uv.lock ./RUN ["uv", "sync", "--frozen", "--no-install-project", "--no-dev"]COPY . .RUN ["uv", "sync", "--frozen", "--no-dev"]
# Runtime stage: copy the venv + app onto a clean python base, nonroot.FROM ghcr.io/quenchworks/images/python:3.14.10 AS runtimeWORKDIR /appENV PATH="/opt/venv/bin:$PATH" \ PYTHONUNBUFFERED=1COPY --from=build /opt/venv /opt/venvCOPY --from=build /app /appUSER 1001EXPOSE 8000CMD ["python", "-m", "app"]This Dockerfile is pinned to the 0.13.9 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://github.com/astral-sh/uv