Required Info:
- Software Version
DRIVE OS 6.0.6 - Target OS
Linux - SDK Manager Version
1.9.2.10884 - Host Machine Version
native Ubuntu Linux 20.04 Host installed with DRIVE OS DOCKER Containers
Describe the bug
in target-docker-container in drive-orinkit, nvidia-container-runtime-csv-mode cannot create sym link of dir.
To Reproduce
in drive-orin-kit, start container using the following scripts and csv files.
with -e NVIDIA_REQUIRE_JETPACK="csv-mounts=all"
to allow all csv files take effect. see Add `nvidia-container-runtime.modes.csv.allowed-files` config option (#11) · Issues · nvidia / container-toolkit / container-toolkit · GitLab
nvidia@tegra-ubuntu:~/zhensheng/orin_ws/nv_driveworks_demo/target/docker/scripts$ ls
gw_base.sh my.bashrc orin_adduser.sh orin_postbuild.sh sdk_adduser.sh sdk_postbuild.sh target_adduser.sh target_postbuild.sh
the driveworks
folder is mapped to the container. using csv files.
sym, /usr/local/driveworks
dir, /usr/local/driveworks-5.10
# in host
nvidia@tegra-ubuntu:~/zhensheng/orin_ws/nv_driveworks_demo/target/docker/scripts$ ll -d /usr/local/driveworks*
lrwxrwxrwx. 1 root root 26 Jan 29 07:52 /usr/local/driveworks -> /usr/local/driveworks-5.10/
drwxr-xr-x. 7 root root 4096 Jan 29 07:49 /usr/local/driveworks-5.10/
# in container
nvidia@in_orin_docker:/usr/local$ ll -d /usr/local/driveworks*
drwxr-xr-x. 7 root root 4096 Jan 29 07:49 /usr/local/driveworks-5.10/
Expected behavior
we can see the sym link of driveworks
folder in container.
/usr/local/driveworks -> /usr/local/driveworks-5.10/
Actual behavior
cannot see this.
Additional context
It’s actually an issue of nvidia-container-runtime.