6ee5dc33ae
Two upstream "use latest" channels recently drifted past what the
project supports and broke `docker build` for the three legacy
Dockerfiles (Dockerfile, docker/Dockerfile.database,
docker/Dockerfile.non_root):
1. Wolfi's `python3` apk meta-package now resolves to CPython
3.14.x, but `pyproject.toml` pins `requires-python = ">=3.10,
<3.14"`. `uv sync ... --python python3` therefore fails with
"interpreter resolved to Python 3.14.x, which is incompatible
with the project's Python requirement".
2. prisma-python's nodeenv now downloads Node 26.2.0, which on
arm64 is dynamically linked against `libatomic.so.1` — a library
wolfi-base doesn't ship. `prisma generate` then fails with
"node: error while loading shared libraries: libatomic.so.1".
Replace both implicit-latest assumptions with explicit pins in all
three Dockerfiles:
* `apk add python-3.13 python-3.13-dev` instead of the meta
`python3` / `python3-dev` (concrete versioned wolfi packages).
* `uv sync ... --python python3.13` (match the apk binary).
* `ENV UV_PYTHON_DOWNLOADS=0` so uv refuses to silently substitute
a managed CPython if the system interpreter ever goes missing.
* `ENV PRISMA_USE_GLOBAL_NODE=true` so `prisma generate` uses the
apk-installed nodejs instead of nodeenv's "latest" Node.
This matches the pattern the newer componentized Dockerfiles
(backend/, gateway/, migrations/) already use. 3.13 is also the
version `docker/tests/nonroot.yaml` already asserts at
`/usr/local/lib/python3.13/site-packages/prisma/`.
|
||
|---|---|---|
| .. | ||
| build_from_pip | ||
| tests | ||
| .env.example | ||
| build_admin_ui.sh | ||
| Dockerfile.database | ||
| Dockerfile.non_root | ||
| entrypoint.sh | ||
| install_auto_router.sh | ||
| prod_entrypoint.sh | ||
| README.md | ||
Docker Development Guide
This guide provides instructions for building and running the LiteLLM application using Docker and Docker Compose.
Prerequisites
- Docker
- Docker Compose
Building and Running the Application
To build and run the application, you will use the docker-compose.yml file located in the root of the project. This file is configured to use the Dockerfile.non_root for a secure, non-root container environment.
1. Set the Master Key
The application requires a LITELLM_MASTER_KEY for signing and validating tokens. You must set this key as an environment variable before running the application.
Create a .env file in the root of the project and add the following line:
LITELLM_MASTER_KEY=your-secret-key
Replace your-secret-key with a strong, randomly generated secret.
2. Build and Run the Containers
Once you have set the LITELLM_MASTER_KEY, you can build and run the containers using the following command:
docker compose up -d --build
This command will:
- Build the Docker image using
Dockerfile.non_root. - Start the
litellm,litellm_db, andprometheusservices in detached mode (-d). - The
--buildflag ensures that the image is rebuilt if there are any changes to the Dockerfile or the application code.
3. Verifying the Application is Running
You can check the status of the running containers with the following command:
docker compose ps
To view the logs of the litellm container, run:
docker compose logs -f litellm
4. Stopping the Application
To stop the running containers, use the following command:
docker compose down
Hardened / Offline Testing
To ensure changes are safe for non-root, read-only root filesystems and restricted egress, always validate with the hardened compose file:
docker compose -f docker-compose.yml -f docker-compose.hardened.yml build --no-cache
docker compose -f docker-compose.yml -f docker-compose.hardened.yml up -d
This setup:
- Builds from
docker/Dockerfile.non_rootwith Prisma engines and Node toolchain baked into the image. - Runs the proxy as a non-root user with a read-only rootfs and only writable tmpfs mounts:
/app/cache(Prisma/NPM cache; backingPRISMA_BINARY_CACHE_DIR,NPM_CONFIG_CACHE,XDG_CACHE_HOME)/app/migrations(Prisma migration workspace; backingLITELLM_MIGRATION_DIR)
- Pre-builds and serves the admin UI from read-only paths:
/var/lib/litellm/ui(pre-restructured Next.js UI with.litellm_ui_readymarker)/var/lib/litellm/assets(UI logos and assets)
- Routes all outbound traffic through a local Squid proxy that denies egress, so Prisma migrations must use the cached CLI and engines.
You should also verify offline Prisma behaviour with:
docker run --rm --network none --entrypoint prisma ghcr.io/berriai/litellm:main-stable --version
This command should succeed (showing engine versions) even with --network none, confirming that Prisma binaries are available without network access.
Troubleshooting
build_admin_ui.sh: not found: This error can occur if the Docker build context is not set correctly. Ensure that you are running thedocker-composecommand from the root of the project.Master key is not initialized: This error means theLITELLM_MASTER_KEYenvironment variable is not set. Make sure you have created a.envfile in the project root with theLITELLM_MASTER_KEYdefined.