Missing library libnvbuf_utils.so.1.0.0 when running docker container

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
1

Hi,
I’m trying to run a docker container over nvcr.io/nvidia/l4t-cuda:10.2.460-runtime, and it fails - missing libraries:

        libatomic.so.1 => /usr/lib/aarch64-linux-gnu/libatomic.so.1 (0x0000007f88bd1000)
        libnvbuf_utils.so.1.0.0 => not found
        libnppig.so.10 => /usr/local/cuda-10.2/targets/aarch64-linux/lib/libnppig.so.10 (0x0000007f8704e000)
        libcuda.so.1 => not found

Running on Jetson AGX. The process runs on the host with no issues.

Running docker with flags --runtime nvidia --privileged returns with error:

docker: Error response from daemon: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: Running hook #1:: error running hook: exit status 1, stdout: , stderr: exec command: [/usr/bin/nvidia-container-cli --load-kmods configure --ldconfig=@/sbin/ldconfig.real --device=all --video --compute --utility --graphics --require=base-only --require=cuda>=10.2 --pid=31826 /var/lib/docker/overlay2/39dd0c300b62690c72bd5de535a824eb338175110244b2445074b4ac4ed50b3f/merged]
nvidia-container-cli: requirement error: invalid expression: unknown.

Can anyone please help?
Thanks,
Adi

3

Hi,

Which JetPack version do you use?
You will need a JetPack 4.6 environment for the container.

We can launch it and run a vectorAdd sample without issue.
Please give it a try.

$ sudo docker run -it --rm --net=host --runtime nvidia -e DISPLAY=$DISPLAY -v /usr/local/cuda-10.2/samples/:/usr/local/cuda-10.2/samples -v /tmp/.X11-unix/:/tmp/.X11-unix nvcr.io/nvidia/l4t-cuda:10.2.460-runtime
...
[Vector addition of 50000 elements]
Copy input data from the host memory to the CUDA device
CUDA kernel launch with 196 blocks of 256 threads
Copy output data from the CUDA device to the host memory
Test PASSED
Done

Thanks.

4

Thank you @AastaLLL,
I see I’m using JetPack 4.5. I’ll upgrade to 4.6 and try again.

me@jetson:~$ sudo apt-cache show nvidia-jetpack
[sudo] password for me: 
Package: nvidia-jetpack
Version: 4.5.1-b17
Architecture: arm64
Maintainer: NVIDIA Corporation
Installed-Size: 194
Depends: nvidia-cuda (= 4.5.1-b17), nvidia-opencv (= 4.5.1-b17), nvidia-cudnn8 (= 4.5.1-b17), nvidia-tensorrt (= 4.5.1-b17), nvidia-visionworks (= 4.5.1-b17), nvidia-container (= 4.5.1-b17), nvidia-vpi (= 4.5.1-b17), nvidia-l4t-jetson-multimedia-api (>> 32.5-0), nvidia-l4t-jetson-multimedia-api (<< 32.6-0)
Homepage: http://developer.nvidia.com/jetson
Priority: standard
Section: metapackages
Filename: pool/main/n/nvidia-jetpack/nvidia-jetpack_4.5.1-b17_arm64.deb
Size: 29372
SHA256: 378f7588e15c35692eb1bed6f336be74f4f396d88fad45af67c68e22b63be04b
SHA1: e41f26a3d8326e9952915eee12fa37e17de3245f
MD5sum: 31b2bd9d0f214f74acaeb3d8e4279e9d
Description: NVIDIA Jetpack Meta Package
Description-md5: ad1462289bdbc54909ae109d1d32c0a8

Package: nvidia-jetpack
Version: 4.5-b129
Architecture: arm64
Maintainer: NVIDIA Corporation
Installed-Size: 194
Depends: nvidia-cuda (= 4.5-b129), nvidia-opencv (= 4.5-b129), nvidia-cudnn8 (= 4.5-b129), nvidia-tensorrt (= 4.5-b129), nvidia-visionworks (= 4.5-b129), nvidia-container (= 4.5-b129), nvidia-vpi (= 4.5-b129), nvidia-l4t-jetson-multimedia-api (>> 32.5-0), nvidia-l4t-jetson-multimedia-api (<< 32.6-0)
Homepage: http://developer.nvidia.com/jetson
Priority: standard
Section: metapackages
Filename: pool/main/n/nvidia-jetpack/nvidia-jetpack_4.5-b129_arm64.deb
Size: 29360
SHA256: 002646e6d81d13526ade23d7c45180014f3cd9e9f5fb0f8896b77dff85d6b9fe
SHA1: cb17547b902b2793e0df86d561809ecdbf7e401f
MD5sum: 06962c42e462f643455d6194d1a2d641
Description: NVIDIA Jetpack Meta Package
Description-md5: ad1462289bdbc54909ae109d1d32c0a8
5

@AastaLLL
Just to update that upgrading to JetPack 4.6 solved the issue.
Thank you again,
Adi