Till recently when we run a Jetson
deepstream-l4t container with
runtime="nvidia" a substantial amount of shared libraries and symbolic links present in the
host are loaded in the container.
The full list can be found on
This kinda ties a certain JetPack version to specific
deepstream-l4t version(s), as there might exist incompatibilities caused by “breaking changes” in the shared libraries.
I think that changed since deepstream-l4t
6.1 as we can find the following information in the documentation:
Since Jetpack 5.0.1 DP, NVIDIA Container Runtime no longer mounts user level libraries like CUDA, cuDNN and TensorRT from the host. These will instead be installed inside the containers.
Is it safe to assume a
JetPack 4.6 installation in the host will be able to handle the following containers without issues?
- deepstream-l4t:6.* (future versions)
Or in order to run a
deepstream-l4t:6.1-triton container is required update the JetPack to