Isaac ROS 4.4 / JetPack 7.2 Container missing nvcc — colcon build fails on isaac_ros_common

Robotics & Edge Computing Robotics - Isaac Isaac ROS
1

Hi everyone,

I am setting up an Isaac ROS 4.4 workspace on a Jetson platform running JetPack 7.2 (L4T R39.2.0).

While my host Jetson environment has the CUDA Toolkit fully configured and functional, the container launched by the new isaac-ros CLI v4.0 fails to find or see the nvcc compiler.

When attempting to execute a standard workspace compilation, colcon build aborts at the isaac_ros_common layer with the following CMake error:

--- stderr: isaac_ros_common                                          
CMake Error at /usr/share/cmake-3.28/Modules/Internal/CMakeCUDAFindToolkit.cmake:104 (message):
  Failed to find nvcc.

  Compiler requires the CUDA toolkit.  Please set the CUDAToolkit_ROOT
  variable.
Call Stack (most recent call first):
  /usr/share/cmake-3.28/Modules/CMakeDetermineCUDACompiler.cmake:89 (cmake_cuda_find_toolkit)
  CMakeLists.txt:24 (enable_language)

Environment Details:

  • Host OS: JetPack 7.2 / L4T R39.2.0 (aarch64)
  • Isaac ROS Release: v4.4
  • Host CUDA/NVCC: Release 13.2, V13.2.78
  • Host /etc/docker/daemon.json configuration
  • {
    "default-runtime": "nvidia",
    "runtimes": {
        "nvidia": {
            "args": [],
            "path": "nvidia-container-runtime"
        }
    }
}

Observed Behaviors & Constraints:

  1. Running /usr/local/cuda/bin/nvcc --version directly inside the container yields bash: /usr/local/cuda/bin/nvcc: No such file or directory, confirming that the host’s CUDA binaries are completely blocked or filtered out from mounting.
  2. Attempting to run echo "export PATH..." >> ~/.bashrc directly inside the container fails completely, yielding: bash: /home/admin/.bashrc: Read-only file system. This is due to the immutable user directory enforcement in the 4.x container stack.
  3. Injecting traditional volume mounts (-v /usr/local/cuda:/usr/local/cuda:ro) via the workspace configurations (.isaac-ros-cli/config.yaml or user-scope variants) seems to be systematically stripped out or ignored by the isaac-ros CLI layer wrapper during container generation.

Questions:

  1. Is anyone else encountering host toolkit mounting filters on JetPack 7.2, and what is the officially supported mechanism to restore nvcc mapping into the ROS 2 Jazzy deployment shell?

Any insights or recommended config patches would be highly appreciated. Thanks!

2

Hello @terminalindigenous,

Welcome to the Isaac ROS forum and thanks for the post!

Isaac ROS 4.4 does not support JetPack 7.2 yet, you could reference this supported platforms matrix. Please downgrade/reflash to the Isaac ROS 4.4 supported JetPack 7.1 / R38.4.0 stack and retry the workspace build.