Holoscan NGC Container Installation
Purpose
Pull and verify the official Holoscan SDK container from NGC (nvcr.io/nvidia/clara-holoscan/holoscan), selecting the right CUDA/arch tag for the host GPU and validating with the bundled Python and C++ examples.
Prerequisites
- Linux host with an NVIDIA GPU and a working driver (
nvidia-smi). - Docker installed and the user in the
dockergroup (orsudo). - NVIDIA Container Toolkit installed (
docker run --gpus allworks). - ~10–20 GB free disk for the image pull.
- Network access to
nvcr.ioanddocs.nvidia.com.
Limitations
- Container images cover only the tag matrix below — no Conda/pip env inside.
- GUI examples require X11 forwarding; this skill runs Holoviz headless to avoid that.
- Tag suffix must match the host GPU/driver (cuda13 / cuda12-dgpu / cuda12-igpu) — wrong suffix → CUDA init failures.
Instructions
- Container repo:
nvcr.io/nvidia/clara-holoscan/holoscan. - The doc page at https://docs.nvidia.com/holoscan/sdk-user-guide/sdk_installation.html is canonical — fetch it if anything below disagrees.
- Work through the steps below in order: pick the tag, verify GPU passthrough and pull, verify with the six examples, then hand off the launch command.
Step 1: Pick the tag
Tag = <version>-<suffix>, e.g. v4.1.0-cuda13. Get the current SDK version from the doc page above; pick the suffix from nvidia-smi (the "CUDA Version" field, top-right of the table header):
The "CUDA Forward Compatibility mode ENABLED" banner is expected — not an error — when the container ships a newer CUDA minor version than the host driver supports. The forward-compat shim lets the container's CUDA runtime work against the older host driver within the same major version.
Step 2: Verify GPU passthrough, then pull
If Docker is missing → install from https://docs.docker.com/engine/install/. If GPU passthrough fails → install the NVIDIA Container Toolkit per https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html, then retry.
Pull (~10–20 GB — warn the user before starting):
Step 3: Verify with six examples
Tests cover: bare Python binding (1a), bare C++ runtime (1b, 2a), Python + Holoviz/Vulkan (2b, 3a), and C++ + Holoviz/Vulkan (3b). Holoviz examples always run headless (inject headless: true into the YAML) — this works whether or not a display is attached and avoids GUI failure modes over SSH.
Step 4: Launch command
- Read https://catalog.ngc.nvidia.com/orgs/nvidia/teams/clara-holoscan/containers/holoscan.
- Explain the docker flags below to the user.
- Refer the user to that link for additional flags (e.g., how to mount V4L2 video devices).
Next:
- Explore:
ls /opt/nvidia/holoscan/examples/ - Walk through one:
/holoscan-explain-example
Troubleshooting
docker: Error response from daemon: could not select device driver "nvidia". NVIDIA Container Toolkit is missing or not configured. Install per the link in Step 2 and restart Docker.- CUDA init failure inside the container. Tag suffix doesn't match the host. Re-check
nvidia-smiCUDA Version and the table in Step 1. - Segmentation fault when launching an example.
ulimit -s 32768wasn't applied inside the container. Use thebash -c "ulimit -s 32768 && ..."pattern shown in Step 3. - Holoviz example hangs / no window over SSH. YAML wasn't patched to
headless: true. Use thesedinjection shown in Step 3. video_replayercan't find data. SetHOLOSCAN_INPUT_PATH=/opt/nvidia/holoscan/data— overrides the YAML's hard-coded path.


