The docker image doesn’t contain nsight-systems, so I exposed the one installed on the host system with the --volume argument of docker. The following is my docker run setting:
–runtime nvidia --net host -it --privileged --cap-add=ALL --ulimit rtprio=99 --tmpfs /tmpfs -v /home/nvidia/ssd/shared_data:/root/shared -e DISPLAY=$DISPLAY -v /tmp/.X11-unix/:/tmp/.X11-unix --volume=“$HOME/.Xauthority:/root/.Xauthority:rw” -v /opt/nvidia/nsight-systems:/opt/nvidia/nsight-systems
After this, running the nsys profile produces segmentation fault for any program inside the docker container. For example:
/opt/nvidia/nsight-systems/2024.2.2/target-linux-tegra-armv8/nsys profile ls
results segfault.
I think this is caused by the mismatch of L4T versions of the docker image and the host (R36.3 vs R36.2). It works fine when nsys is used outside of docker. Please let me know how I can get the nsight-systems CLI for R36.2, or a way to fix this segmentation fault.
I need to use the NVIDIA L4T ML container specifically as I need the libraries installed there. Please let me know a better solution, I don’t want to switch containers.
I couldn’t figure out the instructions on how to build for r36.3 in the repo you sent but I utilized the instructions to install numba from there and carried out the rest of it myself on top of l4t-jetpack:r36.3 container. It works now, thanks!