I am seeing this error when trying to run cd ${ISAAC_ROS_WS}/src/isaac_ros_common && \ ./scripts/run_dev.sh ${ISAAC_ROS_WS} found here in the isaac_ros_visual_slam Quickstart guide:
docker: Error response from daemon: error while creating mount source path '/dev/*': mkdir /dev/*: permission denied.
~/workspaces/isaac_ros-dev/src/isaac_ros_common
I followed these instructions for setting up the Nvidia Container Toolkit using Apt and the rootless Docker configuration. All of that seemed to go smoothly and I can run the docker hello-world in both sudo and rootless mode.
I have an Nvidia 4080 (Driver Version: 535.154.05) and here is the output from running nvcc --version:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2022 NVIDIA Corporation
Built on Wed_Sep_21_10:33:58_PDT_2022
Cuda compilation tools, release 11.8, V11.8.89
Build cuda_11.8.r11.8/compiler.31833905_0
Any ideas on how to fix this problem?
All of the posts say you should not run the run_dev.sh script with sudo so that does not seem like the issue.
Also, isn't it a potential security issue to mount the entire /dev/ directory into a container that runs with privileged access? Maybe I'm not understanding how that works, but it just seemed odd to see -v /dev/*:/dev/* in the docker run command.
I am seeing this error when trying to run
cd ${ISAAC_ROS_WS}/src/isaac_ros_common && \ ./scripts/run_dev.sh ${ISAAC_ROS_WS}found here in theisaac_ros_visual_slamQuickstart guide:I followed these instructions for setting up the Nvidia Container Toolkit using Apt and the rootless Docker configuration. All of that seemed to go smoothly and I can run the docker hello-world in both sudo and rootless mode.
I have an Nvidia 4080 (Driver Version: 535.154.05) and here is the output from running
nvcc --version:Any ideas on how to fix this problem?
All of the posts say you should not run the
run_dev.shscript withsudoso that does not seem like the issue.Also, isn't it a potential security issue to mount the entire
/dev/directory into a container that runs with privileged access? Maybe I'm not understanding how that works, but it just seemed odd to see-v /dev/*:/dev/*in the docker run command.