Skip to content

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

Merged
mudler merged 1 commit into
masterfrom
fix-vllm-omni-install
Sep 19, 2026
Merged

mudler merged 1 commit into
masterfrom
fix-vllm-omni-install

Conversation

@mudler-agent

Copy link
Copy Markdown
Collaborator

Summary

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

Includes 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

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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants