Container fails to start: "read-only file system" error when symlinking `libcuda.so` on Jetson/Tegra

[hsungo]

Description

When running the provided ./build.sh script, the advantech-yolo-vision container fails to start during the initialization phase. The NVIDIA container runtime hook encounters a read-only file system error while trying to create a symlink for /usr/lib/aarch64-linux-gnu/tegra/libcuda.so.

It appears the volume configuration mounts the tegra directory as read-only (:ro), preventing the hook from creating necessary symlinks.

Steps to Reproduce

1. Execute the build script: ./build.sh
2. The container advantech-yolo-vision attempts to start but fails.
3. Check the error logs.

Error Logs

[+] Running 0/1    
 ⠦ Container advantech-yolo-vision  Starting                                                                                                                                                                     11.7s 
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running createContainer hook #0: exit status 1, stdout: , stderr: time="2026-03-11T18:11:25+08:00" level=info msg="Symlinking /var/lib/docker/overlay2/382364687a1e9a4e02b1995ae3e4acc5f34a9a78cb5f47125e411e4b387c8a15/merged/usr/lib/aarch64-linux-gnu/tegra/libcuda.so to libcuda.so.1"
time="2026-03-11T18:11:25+08:00" level=error msg="failed to create link [libcuda.so.1 /usr/lib/aarch64-linux-gnu/tegra/libcuda.so]: failed to create symlink: failed to remove existing file: remove /var/lib/docker/overlay2/382364687a1e9a4e02b1995ae3e4acc5f34a9a78cb5f47125e411e4b387c8a15/merged/usr/lib/aarch64-linux-gnu/tegra/libcuda.so: read-only file system": unknown
[ERROR] 2026-03-11 18:11:25 Failed to start containers