DeepStream 7.1 container incompatible with JetPack 6.2.1 (Driver version mismatch on Jetson Orin Nano)

Please provide complete information as applicable to your setup:

  • Hardware Platform: Jetson Orin Nano

  • DeepStream Version: 7.1

  • JetPack Version: Tested with 6.1, 6.2, and 6.2.1

  • Issue Type: Bug / Compatibility issue

  • How to Reproduce:

    1. Install JetPack 6.2.1 (latest version at the time of writing).

    2. Pull and run the DeepStream 7.1 container (nvcr.io/nvidia/deepstream-l4t:7.1-triton-multiarch).

    3. The following error appears when starting the container:

      This container was built for NVIDIA Driver Release 560.28 or later,
      but version 540.4.0 was detected and compatibility mode is UNAVAILABLE.
      
      

I also tried downgrading JetPack to versions 6.2 and 6.1, but the same issue occurred.
It seems the container requires a newer driver version than the one currently available for the Orin Nano via JetPack.

Is there a compatible DeepStream 7.1 container for JetPack 6.2.1, or a planned update for the base drivers?

Please refer to the doc for how to use docker on DS7.1. nvcr.io/nvidia/deepstream:7.1-triton-multiarch is recommended.

Thank you for your reply. I followed the recommended setup and used the Jetson container as documented. However, the issue persists.

docker run -it  \
  --name dev \
  --network=host \
  --runtime=nvidia \
  --privileged \
  --device=/dev/video0 \
  --device=/dev/video1 \
  -e DISPLAY=$DISPLAY \
  -w /opt/nvidia/deepstream/deepstream-7.1 \
  -v /tmp/.X11-unix/:/tmp/.X11-unix \
  nvcr.io/nvidia/deepstream:7.1-triton-multiarch

Output:

=============================
== Triton Inference Server ==
=============================

NVIDIA Release 24.08 (build 107631426)
Triton Server Version 2.49.0

Copyright (c) 2018-2024, NVIDIA CORPORATION & AFFILIATES.  All rights reserved.

Various files include modifications (c) NVIDIA CORPORATION & AFFILIATES.  All rights reserved.

This container image and its contents are governed by the NVIDIA Deep Learning Container License.
By pulling and using the container, you accept the terms and conditions of this license:
https://developer.nvidia.com/ngc/nvidia-deep-learning-container-license

ERROR: This container was built for NVIDIA Driver Release 560.28 or later, but
       version 540.4.0 was detected and compatibility mode is UNAVAILABLE

This is the same behavior I observed before when using JetPack 6.2.1 on Jetson Orin Nano.

It seems the container was built against a newer driver (560), while JetPack 6.2.1 still ships with driver 540.

Is there any possible workaround to make this container work with the current JetPack driver version, or any recommended way to manually upgrade the L4T driver to match the required version?

Thanks in advance for any guidance.

from the compatibility table, DeepStream requreis Jetpack 6.1, which uses driver 540. you can use “nvidiia-smi” to check. Hence please refer to this link to install Jetpack6.1. then refer to the link in my last comment to start docker.

Thank you for your response.

I installed Jetpack 6.1 as suggested. Here is the output of “nvidia-smi”:

Then, I ran the DeepStream container using the following command:

docker run -it  \
  --name dev \
  --network=host \
  --runtime=nvidia \
  --privileged \
  --device=/dev/video0 \
  --device=/dev/video1 \
  -e DISPLAY=$DISPLAY \
  -w /opt/nvidia/deepstream/deepstream-7.1 \
  -v /tmp/.X11-unix/:/tmp/.X11-unix \
  nvcr.io/nvidia/deepstream:7.1-triton-multiarch

However, I’m still getting the same result:

ERROR: This container was built for NVIDIA Driver Release 560.28 or later, but
       version 540.4.0 was detected and compatibility mode is UNAVAILABLE.

It seems that even with JetPack 6.1 (driver 540.4.0), the DeepStream 7.1 container still requires driver 560 or newer.
Is there any workaround or alternative container that supports JetPack 6.1 / driver 540 on Jetson Orin Nano?

Thanks again for your help and guidance.

Thanks for the sharing! can the applications like test1 run well after printing that error information? if so, Please ignore that tip because this issue can’t be reproduced in the latter versions.

Hi! Since we haven’t heard back from you for a while, we’re assuming everything is resolved and will close this topic. If you need any further help, don’t hesitate to open a new topic. Thanks!