mateo-berri ebdb54d4f0 fix(docker): keep image venvs on the apk python and bump the wolfi digest ... Since the requires-python cap moved to <3.15, uv resolved the project python to 3.14, downloaded a managed interpreter under /root/.local/share/uv that the runtime stage never receives, and every layer-cache-miss image build broke: first at uvloop's cp314 sdist configure step, then, with file/make added, at the runtime stage where the copied venv's python symlink dangles and prisma imports fall through to the system python. UV_PYTHON_DOWNLOADS=0 (already the convention in migrations/backend/gateway) roots the venv on the apk python3. The wolfi-base digest bump is required alongside it: the pinned 08-22 base ships glibc-2.43 while the current apk python-3.13 needs GLIBC_2.44, and wolfi version-names glibc packages so apk upgrade cannot cross that boundary. With the venv on system 3.13 every dependency installs from wheels again, so the file and make packages added for the sdist build are reverted.		2026-08-31 13:32:19 -07:00
..
routes	Merge pull request #26900 from BerriAI/litellm_model-deprecation-alerts-55bc	2026-08-17 18:15:20 -07:00
Dockerfile	fix(docker): keep image venvs on the apk python and bump the wolfi digest	2026-08-31 13:32:19 -07:00
main.py	chore(oss): litellm oss staging 120626 (#30292)	2026-06-12 09:49:25 -07:00