holoscan-install-container
Install Holoscan SDK via the NGC Docker container. Use for container-based installs; not for native apt/pip/Conda installs.
Security Assessment
About holoscan-install-container
This skill installs the NVIDIA Holoscan SDK via its official NGC Docker container and verifies the installation. It solves the problem of getting a correct, GPU-matched Holoscan environment running without native apt/pip/Conda installs: it pulls the official image from nvcr.io/nvidia/clara-holoscan/holoscan, selects the right CUDA/architecture tag for the host GPU, and validates the result against the bundled example programs. It is explicitly scoped to container-based installs and points to the canonical NVIDIA documentation as the source of truth if anything disagrees.
The workflow proceeds in ordered steps: choose the tag by reading the SDK version from the docs and matching a suffix (cuda13, cuda12-dgpu, or cuda12-igpu) to the host's nvidia-smi CUDA version; verify GPU passthrough with a throwaway ubuntu container running nvidia-smi and then pull the image (warning about the 10-20 GB download); verify with six bundled examples spanning bare Python and C++ runtimes and Holoviz/Vulkan rendering; and finally hand off a documented launch command. Holoviz examples are run headless by injecting a headless flag into the example YAML so they work over SSH without X11. The skill documents prerequisites (NVIDIA driver, Docker, NVIDIA Container Toolkit), limitations, and troubleshooting for common driver/toolkit and CUDA-mismatch errors.
It targets developers and researchers deploying Holoscan for medical/edge AI and sensor-processing workloads who prefer containers. The Docker commands use elevated runtime options (CAP_SYS_PTRACE, --ipc=host, raised ulimits, --gpus all) that are standard and necessary for GPU compute containers, and all commands pull from and reference official NVIDIA sources rather than untrusted ones.
FAQ
What are the prerequisites?
A Linux host with an NVIDIA GPU and working driver (nvidia-smi), Docker with the user in the docker group or sudo, the NVIDIA Container Toolkit so '--gpus all' works, about 10-20 GB free disk, and network access to nvcr.io and docs.nvidia.com.
How do I pick the right container tag?
The tag is version plus a suffix. Get the SDK version from the NVIDIA docs page and choose the suffix from nvidia-smi's CUDA Version: cuda13 for 13.x+, cuda12-dgpu for 12.x Ampere/Ada dGPUs, or cuda12-igpu for 12.x ARM64 iGPUs. A wrong suffix causes CUDA init failures.
How is the install verified?
By running six bundled examples covering bare Python bindings, the C++ runtime, tensor interop, and video replay with Holoviz/Vulkan. Holoviz examples are run headless via an injected YAML flag so they work without a display.
What are the known limitations?
The images only cover the documented tag matrix (no Conda/pip env inside), GUI examples require X11 forwarding (so the skill runs Holoviz headless), and the tag suffix must match the host GPU/driver or CUDA initialization fails.
Why do the run commands add capabilities like CAP_SYS_PTRACE and --ipc=host?
These are standard, documented options for GPU compute containers to allow debugging, shared memory, and unlimited memlock/stack for Holoscan workloads; they come straight from NVIDIA's official run instructions.
Install holoscan-install-container
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
nvidia/skills