RUNLOCALAIv38
->Will it run?Best GPUCompareTroubleshootStartLearnPulseModelsHardwareToolsBench
Run check
RUNLOCALAI

Independently operated catalog for local-AI hardware and software. Hand-written verdicts. Source-cited claims. Reproducible commands when we have them.

OP·Fredoline Eruo
DIR
  • Models
  • Hardware
  • Tools
  • Benchmarks
TOOLS
  • Will it run?
  • Compare hardware
  • Cost vs cloud
  • Choose my GPU
  • Prompting kits
  • Quick answers
REF
  • All buyer guides
  • Learn local AI
  • Methodology
  • Glossary
  • Errors KB
  • Trust
EDITOR
  • About
  • Author
  • How we make money
  • Editorial policy
  • Contact
LEGAL
  • Privacy
  • Terms
  • Sitemap
MAIL · MONTHLY DIGEST
Get monthly local AI changes
Monthly recap. No spam.
DISCLOSURE

Some links on this site are affiliate links (Amazon Associates and other first-class retailers). When you buy through them, we earn a small commission at no extra cost to you. Affiliate links do not influence our verdicts — there are cards we rate highly that we don't have affiliate relationships with, and cards that sell well that we refuse to recommend. Read more →

© 2026 runlocalai.coIndependently operated
RUNLOCALAI · v38
Errors / CUDA / NVIDIA / vLLM install picks the wrong CUDA wheel
CUDA / NVIDIA
Verified by owner

vLLM install picks the wrong CUDA wheel

ImportError: libcudart.so.12: cannot open shared object file (typical when the cu124 wheel of vLLM lands on a cu118-only host)
By Fredoline Eruo · Last verified Jun 12, 2026

Cause

Environment: vLLM installed via pip onto a host whose driver/toolkit pair doesn't match the default wheel.

Severity: high — vLLM won't import.

  • Pip's default index ships the latest-CUDA vLLM wheel; older drivers can't load it
  • Mixed conda env where libcudart was upgraded by another package
  • Custom-built PyTorch + pip vLLM landing on different CUDA majors
  • Air-gapped install where the cu118/cu121 wheel needed wasn't downloaded

Solution

1. Use the matching CUDA wheel index for your driver:

# Driver supports CUDA 12.1
pip install vllm --extra-index-url https://download.pytorch.org/whl/cu121
# Or for CUDA 11.8 (older H100/A100 fleets)
pip install vllm==0.4.3 --extra-index-url https://download.pytorch.org/whl/cu118

2. Or install via the official vLLM Docker image (zero CUDA config needed):

docker run --gpus all -p 8000:8000 \
  -v ~/.cache/huggingface:/root/.cache/huggingface \
  vllm/vllm-openai:latest --model meta-llama/Llama-3.1-8B-Instruct

3. Verify the wheel CUDA target after install:

python -c "import torch; print('torch cuda:', torch.version.cuda); \
import vllm; print('vllm version:', vllm.__version__)"

4. Force-reinstall PyTorch first so the toolkit version is pinned before vLLM picks it up:

pip install --force-reinstall torch==2.4.0 \
  --index-url https://download.pytorch.org/whl/cu121
pip install vllm

5. Build vLLM from source when no pre-built wheel matches your stack:

git clone https://github.com/vllm-project/vllm
cd vllm && pip install -e . --no-build-isolation

Build is 10-30 min; only do this if the wheel path is impossible.

Related errors

  • RuntimeError: CUDA error: device-side assert triggered
  • PyTorch: CUDA error: no kernel image is available for execution on the device
  • CUDA runtime version doesn't match the installed driver

Did this fix it?

If your case was different, email Contact support with what you saw and we'll update the page. If it worked but took different commands on your platform, we want to know that too.