Deployment Note: vLLM JIT Path Resolution -nvidia/cu13/lib/-

#5
by MadGoatHaz - opened

Because this checkpoint uses a dynamic activation scheme (W8A8 FP8_DYNAMIC), vLLM falls back to the Triton JIT path during the warmup phase. In isolated environments (like uv or pinned pip virtualenvs), nvrtc throws a runtime failure because libnvrtc-builtins.so.13.0 is localized inside the virtual environment's site-packages (nvidia/cu13/lib/) instead of standard system library paths. This causes tensor-parallel worker sub-processes to crash on initialization.

Adding this dynamic path discovery snippet to the vLLM execution instructions will help cluster operators so they don't have to manually hunt for their virtualenv layout:

# Auto-locate nested CUDA wheel libraries for the linker
export LD_LIBRARY_PATH=$(python -c "import site, os; print(next((os.path.join(p, 'nvidia/cu13/lib') for p in site.getsitepackages() if os.path.isdir(os.path.join(p, 'nvidia/cu13/lib'))), ''))"):$LD_LIBRARY_PATH

# Launch server
uv run vllm serve bottlecapai/ThinkingCap-Qwen3.6-27B-FP8 --tensor-parallel-size 8 ...
BottleCapAI org

We just released new version just 5 minutes after comment. Can you tried it?
I hope it might fix this as well. I tested on clean uv environment because we discovered this problem too.

Sure thing, once the cluster is done with it's current task I will load it up and report back...

Confirmed - Full hugging face pull with vllm and it loaded without issue.

Adamiros changed discussion status to closed

Sign up or log in to comment