-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add documentation for using uv in a Docker image
- Loading branch information
Showing
1 changed file
with
97 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,97 @@ | ||
# Using uv in Docker | ||
|
||
## Installing uv | ||
|
||
uv can be installed by copying from our Docker image: | ||
|
||
```dockerfile | ||
FROM ghcr.io/astral-sh/uv:latest as uv | ||
FROM python:3.12-slim-bullseye | ||
COPY --from=uv /uv /bin/uv | ||
``` | ||
|
||
Or with our standalone installer: | ||
|
||
```dockerfile | ||
FROM python:3.12-slim-bullseye | ||
RUN apt-get update && apt-get install -y curl --no-install-recommends | ||
RUN curl -LsSf https://astral.sh/uv/install.sh | sh | ||
ENV PATH="/root/.cargo/bin/:$PATH" | ||
``` | ||
|
||
Note this requires `curl` to be available. | ||
|
||
## Installing a package | ||
|
||
Once uv is installed in an image, it can be used to install some packages. | ||
|
||
The `--system` flag is safe to use this context, since a container is already isolated. | ||
|
||
```dockerfile | ||
RUN uv pip install --system ruff | ||
``` | ||
|
||
Alternatively, a virtual environment can be created and activated: | ||
|
||
```dockerfile | ||
RUN uv venv /opt/venv | ||
# Use the virtual environment automatically | ||
ENV VIRTUAL_ENV=/opt/venv | ||
# Place entry points in the environment at the front of the path | ||
ENV PATH="/opt/venv/bin:$PATH" | ||
``` | ||
|
||
When using a virtual environment, the `--system` flag should be omitted from uv invocations. | ||
|
||
```dockerfile | ||
RUN uv pip install ruff | ||
``` | ||
|
||
## Installing requirements | ||
|
||
To install requirements files, copy them into the container: | ||
|
||
``` | ||
COPY requirements.txt . | ||
RUN uv pip install -r requirements.txt | ||
``` | ||
|
||
## Installing a project | ||
|
||
When installing a project alongside requirements, it is prudent to separate copying the requirements from the rest of the source code. This allows the dependencies of the project (which do not change often) to be cached separately from the project itself (which changes very frequently). | ||
|
||
``` | ||
COPY pyproject.toml . | ||
RUN uv pip install -r pyproject.toml | ||
COPY . . | ||
RUN uv pip install -e . | ||
``` | ||
|
||
## Optimizations | ||
|
||
### Using uv temporarily | ||
|
||
If uv isn't needed in the final image, the binary can be mounted in each invocation: | ||
|
||
``` | ||
RUN --mount=from=uv,source=/uv,target=/bin/uv \ | ||
uv pip install --system ruff | ||
``` | ||
|
||
### Caching | ||
|
||
A [cache mount](https://docs.docker.com/build/guide/mounts/#add-a-cache-mount) can be used to improve performance across builds: | ||
|
||
``` | ||
RUN --mount=type=cache,target=/root/.cache/uv \ | ||
./uv pip install -r requirements.txt --> | ||
``` | ||
|
||
Note the cache directory's location can be determined with the `uv cache dir` command. | ||
Alternatively, the cache can be set to a constant location: | ||
|
||
``` | ||
ENV UV_CACHE_DIR=/opt/uv-cache/ | ||
``` | ||
|
||
If not mounting the cache, image size can be reduced with `--no-cache` flag. |