fix: preserve vllm-omni imports after backend relocation (#12137)

Use a regular (non-editable) pip/uv install so the package lands in the
venv site-packages. An editable finder records the builder source path,
which breaks after the backend is copied out of the image (#9162).

Adds a regression test (scripts/build/vllm-omni-install_test.sh) that
verifies imports survive relocation with a regular install and fail with
an editable install.

Supersedes #12040 (DCO not signed by contributor).

Assisted-by: MAKI:regolo/glm5.2

Signed-off-by: Ettore Di Giacinto <mudler@localai.io>
Co-authored-by: Ettore Di Giacinto <mudler@localai.io>
This commit is contained in:
mudler-agentandEttore Di Giacinto authored and GitHub committed 2026-09-19 23:39:27 +02:00
1 parent f909bea212
commit 6184a258b3
3 files changed
+460 -5

No files matched your search

+5 -3
View File
@@ -79,11 +79,13 @@ cd vllm-omni/
if [ "$(uname -m)" = "aarch64" ] && [ -f requirements/cuda.txt ]; then
sed -i '/^fa3-fwd[[:space:]]*==/d' requirements/cuda.txt
fi
# Regular (non-editable) install so the package lives in the venv site-packages.
# An editable finder records this builder source path, which breaks after the
# backend is copied out of the image (mudler/LocalAI#9162).
if [ "x${USE_PIP}" == "xtrue" ]; then
pip install ${EXTRA_PIP_INSTALL_FLAGS:-} -e .
pip install ${EXTRA_PIP_INSTALL_FLAGS:-} .
else
uv pip install ${EXTRA_PIP_INSTALL_FLAGS:-} -e .
uv pip install ${EXTRA_PIP_INSTALL_FLAGS:-} .
fi
cd ..