scriptoriumadmin/litellm
1
0
Fork 0
mirror of https://github.com/BerriAI/litellm.git synced 2026-09-13 23:11:40 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 101
litellm/docker/build_from_pip
History
Exact
Yuneng Jiang 8903c3bb06
build(deps): update ddtrace to the 4.x line 
Moves the proxy-runtime ddtrace constraint from >=2.19.0,<3.0 to >=4.8.2,<5.0,
aligns the build_from_pip image pin, and updates the type-only Tracer import to
its current module path (ddtrace.tracer -> ddtrace.trace), which 4.x requires.

Lock delta is ddtrace 2.19.0 -> 4.11.0 plus the removal of legacy-cgi and
xmltodict, which were 2.x-only transitives; neither is imported anywhere in
litellm, enterprise or tests. Lock pinned to 4.11.0 to match internal staging
and the build_from_pip pin rather than floating to the newest 4.x.

Adapted from the staging commit: this line never carried the python_version
constraint split from #33438, so the two-line split collapses to a single
constraint here, and staging's uv.lock hunk was dropped in favour of a lock
re-derived on this line.

(cherry picked from commit edc38eab34)
2026-08-08 12:30:07 -07:00
..
Dockerfile.build_from_pip build(deps): update ddtrace to the 4.x line 2026-08-08 12:30:07 -07:00
litellm_config.yaml ci: run a local fake OpenAI endpoint instead of the shared Railway mock (#30695) 2026-06-17 17:01:13 -07:00
Readme.md (feat) - allow building litellm proxy from pip package (#7633) 2025-01-08 16:36:57 -08:00

Readme.md

Docker to build LiteLLM Proxy from litellm pip package

When to use this ?

If you need to build LiteLLM Proxy from litellm pip package, you can use this Dockerfile as a reference.

Why build from pip package ?

  • If your company has a strict requirement around security / building images you can follow steps outlined here