Skip to content

[docs/integration/docker] add sha pinning tip #10955

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zanieb merged 2 commits into from
Jan 27, 2025
Merged

[docs/integration/docker] add sha pinning tip #10955

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4c0b29e
[docs/integration/docker] add sha pinning tip
ryan-ph Jan 25, 2025
9cb41e2
Update docs/guides/integration/docker.md
zanieb Jan 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/guides/integration/docker.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,6 +110,18 @@ In either case, it is best practice to pin to a specific uv version, e.g., with:
COPY --from=ghcr.io/astral-sh/uv:0.5.24 /uv /uvx /bin/
```

!!! tip

While the Dockerfile example above pins to a specific tag, it's also
possible to pin a specific SHA256. Pinning a specific SHA256 is considered
best practice in environments that require reproducible builds as tags can
be moved across different commit SHAs.

```Dockerfile
# e.g., using a hash from a previous release
COPY --from=ghcr.io/astral-sh/uv@sha256:2381d6aa60c326b71fd40023f921a0a3b8f91b14d5db6b90402e65a635053709 /uv /uvx /bin/
```

Or, with the installer:

```dockerfile
Expand Down