# vLLM Container issue in DGX Spark

**URL:** <https://forums.developer.nvidia.com/t/vllm-container-issue-in-dgx-spark/350723>\
**Category:** DGX Spark / GB10\
**Created:** [November 9, 2025, 9:13pm UTC](https://forums.developer.nvidia.com/t/vllm-container-issue-in-dgx-spark/350723 "2025-11-09T21:13:22Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![pietro\_n](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@pietro\_n](https://forums.developer.nvidia.com/u/pietro_n)\
**Post date:** [November 9, 2025, 9:13pm UTC](https://forums.developer.nvidia.com/t/vllm-container-issue-in-dgx-spark/350723/1 "2025-11-09T21:13:22Z")

</div>

When I try to instal vLLM via a docker - any ideas?:

:/workspace# pip uninstall -y packaging

Found existing installation: packaging 23.2

Uninstalling packaging-23.2:

Successfully uninstalled packaging-23.2

WARNING: Running pip as the ‘root’ user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: [12. Virtual Environments and Packages — Python 3.14.0 documentation](https://pip.pypa.io/warnings/venv) . Use the --root-user-action option if you know what you are doing and want to suppress this warning.

root@aaa:/workspace# pip install packaging\>=24.2

DEPRECATION: Loading egg at /usr/local/lib/python3.12/dist-packages/dill-0.3.9-py3.12.egg is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to use pip for package installation. Discussion can be found at [Remove additional detection of `.egg` packages when using the `importlib.metadata` backend · Issue #12330 · pypa/pip · GitHub](https://github.com/pypa/pip/issues/12330)

DEPRECATION: Loading egg at /usr/local/lib/python3.12/dist-packages/lightning\_utilities-0.14.0-py3.12.egg is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to use pip for package installation. Discussion can be found at [Remove additional detection of `.egg` packages when using the `importlib.metadata` backend · Issue #12330 · pypa/pip · GitHub](https://github.com/pypa/pip/issues/12330)

DEPRECATION: Loading egg at /usr/local/lib/python3.12/dist-packages/lightning\_thunder-0.2.2.dev0-py3.12.egg is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to use pip for package installation. Discussion can be found at [Remove additional detection of `.egg` packages when using the `importlib.metadata` backend · Issue #12330 · pypa/pip · GitHub](https://github.com/pypa/pip/issues/12330)

DEPRECATION: Loading egg at /usr/local/lib/python3.12/dist-packages/looseversion-1.3.0-py3.12.egg is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to use pip for package installation. Discussion can be found at [Remove additional detection of `.egg` packages when using the `importlib.metadata` backend · Issue #12330 · pypa/pip · GitHub](https://github.com/pypa/pip/issues/12330)

DEPRECATION: Loading egg at /usr/local/lib/python3.12/dist-packages/opt\_einsum-3.4.0-py3.12.egg is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to use pip for package installation. Discussion can be found at [Remove additional detection of `.egg` packages when using the `importlib.metadata` backend · Issue #12330 · pypa/pip · GitHub](https://github.com/pypa/pip/issues/12330)

DEPRECATION: Loading egg at /usr/local/lib/python3.12/dist-packages/nvfuser-0.2.26a0+c5e1555-py3.12-linux-aarch64.egg is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to use pip for package installation. Discussion can be found at [Remove additional detection of `.egg` packages when using the `importlib.metadata` backend · Issue #12330 · pypa/pip · GitHub](https://github.com/pypa/pip/issues/12330)

WARNING: Running pip as the ‘root’ user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: [12. Virtual Environments and Packages — Python 3.14.0 documentation](https://pip.pypa.io/warnings/venv) . Use the --root-user-action option if you know what you are doing and want to suppress this warning.

root@aaa:/workspace# pip install vllm

DEPRECATION: Loading egg at /usr/local/lib/python3.12/dist-packages/dill-0.3.9-py3.12.egg is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to use pip for package installation. Discussion can be found at [Remove additional detection of `.egg` packages when using the `importlib.metadata` backend · Issue #12330 · pypa/pip · GitHub](https://github.com/pypa/pip/issues/12330)

DEPRECATION: Loading egg at /usr/local/lib/python3.12/dist-packages/lightning\_utilities-0.14.0-py3.12.egg is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to use pip for package installation. Discussion can be found at [Remove additional detection of `.egg` packages when using the `importlib.metadata` backend · Issue #12330 · pypa/pip · GitHub](https://github.com/pypa/pip/issues/12330)

DEPRECATION: Loading egg at /usr/local/lib/python3.12/dist-packages/lightning\_thunder-0.2.2.dev0-py3.12.egg is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to use pip for package installation. Discussion can be found at [Remove additional detection of `.egg` packages when using the `importlib.metadata` backend · Issue #12330 · pypa/pip · GitHub](https://github.com/pypa/pip/issues/12330)

DEPRECATION: Loading egg at /usr/local/lib/python3.12/dist-packages/looseversion-1.3.0-py3.12.egg is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to use pip for package installation. Discussion can be found at [Remove additional detection of `.egg` packages when using the `importlib.metadata` backend · Issue #12330 · pypa/pip · GitHub](https://github.com/pypa/pip/issues/12330)

DEPRECATION: Loading egg at /usr/local/lib/python3.12/dist-packages/opt\_einsum-3.4.0-py3.12.egg is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to use pip for package installation. Discussion can be found at [Remove additional detection of `.egg` packages when using the `importlib.metadata` backend · Issue #12330 · pypa/pip · GitHub](https://github.com/pypa/pip/issues/12330)

DEPRECATION: Loading egg at /usr/local/lib/python3.12/dist-packages/nvfuser-0.2.26a0+c5e1555-py3.12-linux-aarch64.egg is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to use pip for package installation. Discussion can be found at [Remove additional detection of `.egg` packages when using the `importlib.metadata` backend · Issue #12330 · pypa/pip · GitHub](https://github.com/pypa/pip/issues/12330)

Collecting vllm

Using cached vllm-0.11.0-cp38-abi3-manylinux2014\_aarch64.whl.metadata (17 kB)

Requirement already satisfied: regex in /usr/local/lib/python3.12/dist-packages (from vllm) (2024.11.6)

Requirement already satisfied: cachetools in /usr/local/lib/python3.12/dist-packages (from vllm) (5.5.2)

Requirement already satisfied: psutil in /usr/local/lib/python3.12/dist-packages (from vllm) (7.0.0)

Collecting sentencepiece (from vllm)

Using cached sentencepiece-0.2.1-cp312-cp312-manylinux\_2\_27\_aarch64.manylinux\_2\_28\_aarch64.whl.metadata (10 kB)

Requirement already satisfied: numpy in /usr/local/lib/python3.12/dist-packages (from vllm) (1.26.4)

Requirement already satisfied: requests\>=2.26.0 in /usr/local/lib/python3.12/dist-packages (from vllm) (2.32.3)

Requirement already satisfied: tqdm in /usr/local/lib/python3.12/dist-packages (from vllm) (4.67.1)

Collecting blake3 (from vllm)

Using cached blake3-1.0.8-cp312-cp312-manylinux\_2\_17\_aarch64.manylinux2014\_aarch64.whl.metadata (4.6 kB)

Collecting py-cpuinfo (from vllm)

Using cached py\_cpuinfo-9.0.0-py3-none-any.whl.metadata (794 bytes)

Collecting transformers\>=4.55.2 (from vllm)

Using cached transformers-4.57.1-py3-none-any.whl.metadata (43 kB)

Collecting tokenizers\>=0.21.1 (from vllm)

Using cached tokenizers-0.22.1-cp39-abi3-manylinux\_2\_17\_aarch64.manylinux2014\_aarch64.whl.metadata (6.8 kB)

Requirement already satisfied: protobuf in /usr/local/lib/python3.12/dist-packages (from vllm) (4.24.4)

Collecting fastapi\>=0.115.0 (from fastapi[standard]\>=0.115.0-\>vllm)

Using cached fastapi-0.121.1-py3-none-any.whl.metadata (28 kB)

Requirement already satisfied: aiohttp in /usr/local/lib/python3.12/dist-packages (from vllm) (3.11.13)

Collecting openai\>=1.99.1 (from vllm)

Using cached openai-2.7.1-py3-none-any.whl.metadata (29 kB)

INFO: pip is looking at multiple versions of vllm to determine which version is compatible with other requirements. This could take a while.

Collecting vllm

Using cached vllm-0.10.2-cp38-abi3-manylinux2014\_aarch64.whl.metadata (16 kB)

Using cached vllm-0.10.1.1.tar.gz (10.5 MB)

Installing build dependencies … error

**error** : **subprocess-exited-with-error**

× pip subprocess to install build dependencies did not run successfully.

│ exit code: **1**

╰─\> [15 lines of output]

```
  Collecting cmake>=3.26.1

    Using cached cmake-3.31.6-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (6.3 kB)

  Collecting ninja

    Using cached ninja-1.11.1.3-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (5.3 kB)

  ERROR: Cannot install packaging>=24.2 because these package versions have conflicting dependencies.

  The conflict is caused by:

      The user requested packaging>=24.2

      The user requested (constraint) packaging==23.2

  To fix this you could try to:

  1\. loosen the range of package versions you've specified

  2\. remove package versions to allow pip to attempt to solve the dependency conflict

  ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

  \[end of output\]

```

**note** : This error originates from a subprocess, and is likely not a problem with pip.

**error** : **subprocess-exited-with-error**

× pip subprocess to install build dependencies did not run successfully.

│ exit code: **1**

╰─\> See above for output.

**note** : This error originates from a subprocess, and is likely not a problem with pip.

---

<div class="post-metadata">

**Author:** ![raphael.amorim](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/raphael.amorim/32/446733_2.png) [@raphael.amorim](https://forums.developer.nvidia.com/u/raphael.amorim)\
**Post date:** [November 9, 2025, 9:36pm UTC](https://forums.developer.nvidia.com/t/vllm-container-issue-in-dgx-spark/350723/2 "2025-11-09T21:36:41Z")

</div>

Try to use it with this docker file: [Running nvidia/Nemotron-Nano-VL-12B-V2-NVFP4-QAD on your spark](https://forums.developer.nvidia.com/t/running-nvidia-nemotron-nano-vl-12b-v2-nvfp4-qad-on-your-spark/350349).  
I’m using latest vLLM main version, but you can use any other tag.

---

<div class="post-metadata">

**Author:** ![pietro\_n](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@pietro\_n](https://forums.developer.nvidia.com/u/pietro_n)\
**Post date:** [November 10, 2025, 6:58pm UTC](https://forums.developer.nvidia.com/t/vllm-container-issue-in-dgx-spark/350723/3 "2025-11-10T18:58:00Z")

</div>

thanks but I dont think this addresses my issue, I can’t install vLLM.

---

<div class="post-metadata">

**Author:** ![abull](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/abull/32/382649_2.png) [@abull](https://forums.developer.nvidia.com/u/abull)\
**Post date:** [November 10, 2025, 7:43pm UTC](https://forums.developer.nvidia.com/t/vllm-container-issue-in-dgx-spark/350723/4 "2025-11-10T19:43:28Z")

</div>

Take a look at this playbook and let us know if this helps answer your questions. [Install and Use vLLM for Inference | DGX Spark](https://build.nvidia.com/spark/vllm)

---

<div class="post-metadata">

**Author:** ![pietro\_n](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@pietro\_n](https://forums.developer.nvidia.com/u/pietro_n)\
**Post date:** [November 11, 2025, 7:06am UTC](https://forums.developer.nvidia.com/t/vllm-container-issue-in-dgx-spark/350723/5 "2025-11-11T07:06:27Z")

</div>

this worked abull - thank you.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\
**Post date:** [November 25, 2025, 7:07am UTC](https://forums.developer.nvidia.com/t/vllm-container-issue-in-dgx-spark/350723/6 "2025-11-25T07:07:24Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.