Build fails on aarch64 due to virtual cuDNN package: libcudnn9 needs explicit provider (libcudnn9-cuda-12)

While building isaac_ros_common for Jetson Orin Nano (JetPack r36.4, Ubuntu 22.04, base nvcr.io/nvidia/12.6.11-devel-aarch64-ubuntu22.04) using ./build_images_layser.sh -i aarch64, the Docker build fails at the CUDA install step with “E: Package 'libcudnn9' has no installation candidate.”

In the current Dockerfile.aarch64, libcudnn9 is specified, but on Ubuntu 22.04 with the NVIDIA repos this is a virtual package provided by libcudnn9-cuda-12 and libcudnn9-cuda-13.

Because the image installs CUDA 12.6 (cuda-toolkit-12-6, etc.), apt requires the explicit provider libcudnn9-cuda-12.

Replacing libcudnn9 with libcudnn9-cuda-12 resolves the build immediately; optionally pinning to 9.12.0.46-1 improves reproducibility.

It may also be worth removing the deprecated --force-yes in the same line.

Could the Dockerfile be updated to use libcudnn9-cuda-12 (or a conditional/provider-agnostic approach based on the selected CUDA version) to prevent build breaks on aarch64?

Open Dockerfile.aarch64 and inspect the CUDA package installation line used by ./build_images_layser.sh -i aarch64. Verify the available cuDNN provider for the CUDA 12.6 base image, then confirm that the Jetson Orin Nano image build completes without the libcudnn9 installation error.