Holoscan SDK
The Holoscan SDK CUDA 13 Python Wheel is part of NVIDIA Holoscan, the AI sensor processing platform that combines hardware systems for low-latency sensor and network connectivity, optimized libraries for data processing and AI, and core microservices to run streaming, imaging, and other applications, from embedded to edge to cloud. It can be used to build streaming AI pipelines for a variety of domains, including Medical Devices, High Performance Computing at the Edge, Industrial Inspection and more.
The Core distribution includes holoscan.testing for standalone operator tests,
with public typing and a separately linked native testing library. Install pytest
separately to run the examples; no testing-only wheel or GPU Python array package
is required. Plain import holoscan does not eagerly import testing.
Getting Started
Visit the Holoscan User Guide to get started with the Holoscan SDK.
Prerequisites
- Prerequisites for each supported platform are documented in the user guide. Note that the python wheels have many optional dependencies which you may install manually based on your needs (see compatibility matrix at the bottom).
- The Holoscan SDK python wheels are tested on Ubuntu 24.04. They are generally expected to work on any Linux distribution with glibc 2.39 or above (see output of
ldd --version) and CUDA Runtime 13.0 or above. - Python: 3.12 to 3.14
Troubleshooting
ERROR: Could not find a version that satisfies the requirement holoscan-core-cu13==<version> ERROR: No matching distribution found for holoscan-core-cu13==<version>
The latest version of the wheels was built and tested on Ubuntu 24.04 with glibc 2.39. You may need to switch to a Linux distribution with a more recent version of glibc (check your version with ldd --version), or use the Holoscan SDK NGC container instead.
libc.so.6: version 'GLIBC_2.32 not found libstdc++.so.6: version `GLIBCXX_3.4.29` not found
Same as above.
ImportError: libcudart.so.13: cannot open shared object file: No such file or directory
CUDA runtime is missing from your system (required even for CPU only pipelines).
-
x86_64: two options
- A) System Installation: Follow the official installation steps for installing the CUDA Toolkit.
- B) PIP installation:
-
For
holoscan-core-cu13:python3 -m pip install nvidia-cuda-runtime==13.*
-
Export the CUDA runtime library path:
export CUDA_WHL_LIB_DIR=$(python3 -c 'import nvidia.cuda_runtime; print(nvidia.cuda_runtime.__path__[0])')/lib export LD_LIBRARY_PATH="$CUDA_WHL_LIB_DIR:$LD_LIBRARY_PATH"
-
-
Jetson Thor: Re-install JetPack 7.0.
-
IGX Orin:
holoscan-core-cu13does not support IGX OS 1.x. -
Jetson Orin:
holoscan-core-cu13does not support Jetpack 6.
catastrophic error: cannot open source file "vector_types.h"
CUDA Runtime headers are missing from your system.
Resolution: same as above.
Reference: https://docs.cupy.dev/en/latest/install.html#cupy-always-raises-nvrtc-error-compilation-6
Error: libnvinfer.so.8: cannot open shared object file: No such file or directory ... Error: libnvonnxparser.so.8: cannot open shared object file: No such file or directory
TensorRT is missing from your system (note that it is only needed by the holoscan.operators.InferenceOp operator.).
-
x86_64:
-
A) System Installation: Follow the official installation steps.
-
B) PIP installation:
python3 -m pip install tensorrt-libs~=8.6.1 --index-url https://pypi.nvidia.com export TRT_WHL_LIB_DIR=$(python3 -c 'import tensorrt_libs; print(tensorrt_libs.__path__[0])') export CUDNN_WHL_LIB_DIR=$(python3 -c 'import nvidia.cudnn; print(nvidia.cudnn.__path__[0])')/lib export CUBLAS_WHL_LIB_DIR=$(python3 -c 'import nvidia.cublas; print(nvidia.cublas.__path__[0])')/lib export LD_LIBRARY_PATH="$TRT_WHL_LIB_DIR:$CUDNN_WHL_LIB_DIR:$CUBLAS_WHL_LIB_DIR:$LD_LIBRARY_PATH"
-
-
Jetson Thor: Re-install JetPack 7.0.
-
IGX Orin:
holoscan-core-cu13does not support IGX OS 1.x. -
Jetson Orin:
holoscan-core-cu13does not support Jetpack 6.
Metadata
Release files for holoscan-core-cu13 5.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| holoscan_core_cu13-5.0.0-cp312-abi3-manylinux_2_39_x86_64.whl | CPython 3.12 | abi3 | Linux glibc 2.39+ x86-64 | Details for holoscan_core_cu13-5.0.0-cp312-abi3-manylinux_2_39_x86_64.whl |
| holoscan_core_cu13-5.0.0-cp312-abi3-manylinux_2_39_aarch64.whl | CPython 3.12 | abi3 | Linux glibc 2.39+ ARM64 | Details for holoscan_core_cu13-5.0.0-cp312-abi3-manylinux_2_39_aarch64.whl |
Total release size: 19.2 MB
Release files / holoscan_core_cu13-5.0.0-cp312-abi3-manylinux_2_39_x86_64.whl
| Download URL | holoscan_core_cu13-5.0.0-cp312-abi3-manylinux_2_39_x86_64.whl |
|---|---|
| Size | 10.0 MB |
| Tags | CPython 3.12 Linux glibc 2.39+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
af71d49439ba3f93c664059faabaa916faae0f9ac8a59699e8e7a289b57cf358
|
|
BLAKE2b-256 checksum How to use checksums |
23c0fe2cdd075a6490591e12a9c538d6861e413d979153c5c80e7fb6e82662d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Release files / holoscan_core_cu13-5.0.0-cp312-abi3-manylinux_2_39_aarch64.whl
| Download URL | holoscan_core_cu13-5.0.0-cp312-abi3-manylinux_2_39_aarch64.whl |
|---|---|
| Size | 9.2 MB |
| Tags | CPython 3.12 Linux glibc 2.39+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
e12b983638dc36206ea178f95db46cdbb6f03db5e6bd5a1de4023c74aa12de5b
|
|
BLAKE2b-256 checksum How to use checksums |
432e8288edf5679461c9d43036186a94670403da2d80f5781aaac7a462fd0a69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Security for holoscan-core-cu13 5.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.