# Tegra libraries are missing on Nvidia L4Tbase docker Image **URL:** \ **Category:** Jetson Nano\ **Tags:** docker\ **Created:** [July 19, 2022, 1:32pm UTC](https://forums.developer.nvidia.com/t/tegra-libraries-are-missing-on-nvidia-l4tbase-docker-image/221218 "2022-07-19T13:32:28Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![florianC31](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@florianC31](https://forums.developer.nvidia.com/u/florianC31)\ **Post date:** [July 19, 2022, 1:32pm UTC](https://forums.developer.nvidia.com/t/tegra-libraries-are-missing-on-nvidia-l4tbase-docker-image/221218/1 "2022-07-19T13:32:28Z")
Hello, I am currently working on the Jetson Nano Developer Kit 2GB with docker and a ZED2i camera from Stereolabs. I’m using the Nvidia Docker base image “[nvcr.io/nvidia/l4t-base:r32.7.1](http://nvcr.io/nvidia/l4t-base:r32.7.1)”. When I try to compile my C++ project using ZED SDK, I need several libraries which should be present in`/usr/lib/aarch64-linux-gnu/tegra`. However, the entire tegra folder is missing in this docker image. When I check on the Jetson system (which has been flashed with the Jetpack 4.6.1), the `/usr/lib/aarch64-linux-gnu/tegra` folder exists with all expected libraries. As a temporary solution, I copied all this folder from the Jetson to my Docker container and it works properly. **However, I would want to know if it’s normal that this folder is missing, and, in this case, how install all these Tegra libraries properly.** Tank you for your help. ---
**Author:** ![dusty\_nv](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/dusty_nv/32/14043_2.png) [@dusty\_nv](https://forums.developer.nvidia.com/u/dusty_nv)\ **Post date:** [July 19, 2022, 5:56pm UTC](https://forums.developer.nvidia.com/t/tegra-libraries-are-missing-on-nvidia-l4tbase-docker-image/221218/2 "2022-07-19T17:56:57Z")
Hi @florianC31, you can check which libraries from `/usr/lib/aarch64-linux-gnu/tegra/` that should be mounted into l4t-base container (and containers that derive from l4t-base) when `--runtime nvidia` is used by checking the file `/etc/nvidia-container-runtime/host-files-for-container.d.csv` Are you starting l4t-base with `--runtime nvidia` ? Or if you are doing a `docker build` operation, have you set your default docker runtime to nvidia like shown here: [https://github.com/dusty-nv/jetson-containers#docker-default-runtime](https://github.com/dusty-nv/jetson-containers#docker-default-runtime) ---
**Author:** ![florianC31](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@florianC31](https://forums.developer.nvidia.com/u/florianC31)\ **Post date:** [July 20, 2022, 7:32am UTC](https://forums.developer.nvidia.com/t/tegra-libraries-are-missing-on-nvidia-l4tbase-docker-image/221218/3 "2022-07-20T07:32:54Z")
You’re right, the issue came from missing “–runtime nvidia”. I already added this parameter in my Docker Compose a few weeks ago, but yesterday I create an intermediary compilation docker and I forgot to add it… And when I made some tests directly on Nvidia images I forgot too… So, I added in default parameters to not be stuck any more in the future. Thanks for the tips ! ---
**Author:** ![dusty\_nv](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/dusty_nv/32/14043_2.png) [@dusty\_nv](https://forums.developer.nvidia.com/u/dusty_nv)\ **Post date:** [July 20, 2022, 1:05pm UTC](https://forums.developer.nvidia.com/t/tegra-libraries-are-missing-on-nvidia-l4tbase-docker-image/221218/4 "2022-07-20T13:05:53Z")
OK no worries, glad that you got it figured out! ---
**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\ **Post date:** [August 3, 2022, 1:06pm UTC](https://forums.developer.nvidia.com/t/tegra-libraries-are-missing-on-nvidia-l4tbase-docker-image/221218/5 "2022-08-03T13:06:06Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.