DeepStream 8.0 / 7.1 compatibility issue on Jetson Orin Nano Super with JetPack 7.2 / Jetson Linux R39.2

Hello NVIDIA DeepStream team,

I am validating DeepStream sample inference on a Jetson Orin Nano Developer Kit / Orin Nano Super setup and need confirmation about the correct DeepStream Docker image/tag for this platform.

Device / Host Setup

Device:

  • NVIDIA Jetson Orin Nano Developer Kit
  • JetPack: 7.2
  • Jetson Linux / L4T: R39.2.0
  • Ubuntu: 24.04.4 LTS
  • Python: 3.12.3
  • Docker: 29.1.3
  • Docker Compose: v2.40.3

Docker was tested successfully with hello-world.

The goal is to validate a standard DeepStream sample inference pipeline on this Jetson before integrating DeepStream into an edge video analytics application.


DeepStream 8.0 Test

Docker image used:

nvcr.io/nvidia/deepstream:8.0-samples-multiarch

Version output from inside the container:

deepstream-app version 8.0.0
DeepStreamSDK 8.0.0
CUDA Driver Version: 13.2
CUDA Runtime Version: 13.0
TensorRT Version: 10.13
cuDNN Version: 9.12
libNVWarp360 Version: 2.0.1d3

The DS8 container starts correctly. NVIDIA runtime is visible. nvinfer is also registered successfully:

Long-name: NvInfer plugin
Description: Nvidia DeepStreamSDK TensorRT plugin
Version: 8.0.0

I tested the sample config:

/opt/nvidia/deepstream/deepstream-8.0/samples/configs/deepstream-app/source4_1080p_dec_infer-resnet_tracker_sgie_tiled_display.txt

To avoid display/EGL issues, I changed only sink0 to fakesink/headless:

cd /opt/nvidia/deepstream/deepstream-8.0/samples/configs/deepstream-app
rm -f ds8_headless_test.txt
cp source4_1080p_dec_infer-resnet_tracker_sgie_tiled_display.txt ds8_headless_test.txt
sed -i '/^\[sink0\]/,/^\[sink1\]/{s/^type=.*/type=1/; s/^sync=.*/sync=0/}' ds8_headless_test.txt
timeout 30s deepstream-app -c ds8_headless_test.txt 2>&1 | tee /tmp/ds8_headless_test.log

The pipeline reaches nvinfer and TensorRT engine creation, but fails here:

NvDsInferContextImpl::deserializeEngineAndBackend():
deserialize engine from file:
../../models/Secondary_VehicleMake/resnet18_vehiclemakenet_pruned.onnx_b16_gpu0_fp16.engine failed

NvDsInferContextImpl::generateBackendContext():
deserialize backend context from engine failed, try rebuild

NvDsInferContextImpl::buildModel():
Trying to create engine from model files

ERROR: [TRT]: IBuilder::buildSerializedNetwork: Error Code 9: API Usage Error
(Target GPU SM 87 is not supported by this TensorRT release.
In checkCurrentSMEnabled at optimizer/common/builderHelpers.cpp:707)

timeout: the monitored command dumped core

I also confirmed that the DS8 sample image does not contain prebuilt .engine or .plan files under the samples directory:

find /opt/nvidia/deepstream/deepstream-8.0/samples -type f \( -name "*.engine" -o -name "*.plan" \) | sort

This returned no engine/plan files.

The configs reference ONNX files and expected engine files, for example:

onnx-file=../../models/Secondary_VehicleMake/resnet18_vehiclemakenet_pruned.onnx
model-engine-file=../../models/Secondary_VehicleMake/resnet18_vehiclemakenet_pruned.onnx_b16_gpu0_fp16.engine

The ONNX files exist, but the .engine files do not. Therefore DeepStream tries to build the TensorRT engine at runtime and fails with SM87 unsupported.

I also installed common GStreamer packages inside the DS8 container and repeated the headless test. The result was unchanged. nvinfer still loads correctly, and the failure remains at TensorRT engine build with SM87 unsupported.


DeepStream 7.1 Fallback Test

I also tested:

nvcr.io/nvidia/deepstream:7.1-samples-multiarch

Image pulled successfully.

Version output:

deepstream-app version 7.1.0
DeepStreamSDK 7.1.0
CUDA Driver Version: 13.2
CUDA Runtime Version: 12.6
TensorRT Version: 10.3
cuDNN Version: 9.0
Dewarper: not found

I tried the DS7.1 INT8 source4 sample:

cd /opt/nvidia/deepstream/deepstream-7.1/samples/configs/deepstream-app
rm -f ds71_headless_test.txt
cp source4_1080p_dec_infer-resnet_tracker_sgie_tiled_display_int8.txt ds71_headless_test.txt
sed -i '/^\[sink0\]/,/^\[sink1\]/{s/^type=.*/type=1/; s/^sync=.*/sync=0/}' ds71_headless_test.txt
timeout 30s deepstream-app -c ds71_headless_test.txt 2>&1 | tee /tmp/ds71_headless_test.log

This failed before inference. Many NVIDIA/DeepStream GStreamer plugins failed with undefined symbol errors, for example:

Failed to load plugin 'libgstnvvideo4linux2.so':
undefined symbol: g_once_init_leave_pointer

Failed to load plugin 'libnvdsgst_deepstream_bins.so':
libnvdsbufferpool.so.1.0.0: undefined symbol: g_once_init_enter_pointer

Failed to load plugin 'libnvdsgst_multistream.so':
libnvdsbufferpool.so.1.0.0: undefined symbol: g_once_init_enter_pointer

Then DeepStream failed to create the source muxer:

** ERROR: <create_multi_source_bin:1520>: Failed to create element 'src_bin_muxer'
** ERROR: <create_multi_source_bin:1608>: create_multi_source_bin failed
** ERROR: <create_pipeline:1927>: create_pipeline failed
** ERROR: <main:695>: Failed to create pipeline
Quitting
App run failed

I checked nvstreammux:

gst-inspect-1.0 nvstreammux

Result:

No such element or plugin 'nvstreammux'

But the plugin file exists:

find /usr/lib /opt/nvidia -name "*multistream*" -o -name "*deepstream_bins*" 2>/dev/null

Output included:

/opt/nvidia/deepstream/deepstream-7.1/lib/gst-plugins/libnvdsgst_deepstream_bins.so
/opt/nvidia/deepstream/deepstream-7.1/lib/gst-plugins/libnvdsgst_multistream.so
/opt/nvidia/deepstream/deepstream-7.1/lib/gst-plugins/libnvdsgst_multistreamtiler.so

Direct plugin inspection shows the actual load issue:

GST_DEBUG=3 GST_PLUGIN_PATH=/opt/nvidia/deepstream/deepstream-7.1/lib/gst-plugins gst-inspect-1.0 /opt/nvidia/deepstream/deepstream-7.1/lib/gst-plugins/libnvdsgst_multistream.so

Error:

Opening module failed:
/usr/lib/aarch64-linux-gnu/nvidia/libnvdsbufferpool.so.1.0.0:
undefined symbol: g_once_init_enter_pointer

So DS7.1 appears to have plugin ABI/library mismatch on this JetPack 7.2 / R39.2 host.


Laptop Environment Note

On my laptop, I also have a DeepStream 8.0 Docker image that can report versions:

DeepStream: 8.0.0
CUDA container banner: 12.8.1
CUDA runtime: 12.9
TensorRT: 10.9
cuDNN: 9.8

However, in that laptop Docker run, GPU is not available:

NVIDIA Driver was not detected

So I am not treating the laptop result as a valid GPU inference test. Also, I understand that TensorRT .engine files are not safely portable from laptop to Jetson because they are tied to GPU architecture, TensorRT version, CUDA stack, batch/profile, and platform.


Summary of Current Results

Stack Result
Jetson Orin Nano + JP7.2/R39.2 + DS8.0 samples multiarch Container starts, nvinfer loads, pipeline reaches TensorRT, but engine build fails with Target GPU SM 87 is not supported by this TensorRT release
Jetson Orin Nano + JP7.2/R39.2 + DS7.1 samples multiarch Container starts, but important NVIDIA/DeepStream GStreamer plugins fail with undefined symbol errors; nvstreammux is not registered; pipeline fails before inference
Laptop DS8 image Version command works, but GPU is not available in Docker, so not a valid inference comparison

Questions

  1. What is the correct NVIDIA-supported DeepStream Docker image/tag for Jetson Orin Nano Developer Kit / Orin Nano Super running JetPack 7.2 / Jetson Linux R39.2?

  2. Is nvcr.io/nvidia/deepstream:8.0-samples-multiarch expected to support TensorRT engine generation for Orin Nano SM87 on JetPack 7.2 / R39.2?

  3. If DeepStream 8.0 is supported for this device, should the TensorRT version inside the container be different from TensorRT 10.13?

  4. Is the Target GPU SM 87 is not supported by this TensorRT release error expected with this DS8.0 image on Orin Nano, or does it indicate that I am using the wrong image/tag?

  5. For JetPack 7.2 / R39.2 on Orin Nano, should we use a different DeepStream 8.x image, a Jetson-specific L4T image, or another container tag?

  6. Is DeepStream 7.1 expected to work on JetPack 7.2 / R39.2, or are the undefined symbol: g_once_init_enter_pointer errors expected because DS7.1 is built for an older JetPack/L4T generation?

  7. Should we reflash the Jetson to an earlier JetPack version if we need DeepStream 7.1 support, or is there a supported DeepStream 8 image for Orin Nano on JP7.2/R39.2?

  8. Are there any required additional host packages, runtime flags, or NVIDIA container runtime settings needed for this exact Orin Nano JP7.2/R39.2 setup?

The main goal is to identify the officially supported DeepStream + TensorRT + CUDA container stack for Jetson Orin Nano / Orin Nano Super on JetPack 7.2 / Jetson Linux R39.2.

Hello @pradeep_prabhu!

Based on the title and content of your topic, it looks like it may receive better visibility and feedback in a different category. We took the liberty of moving it for you.

If this was an incorrect assessment, please send me a direct message.

Disclaimer: this moderation suggestion and message were generated with AI assistance.

Hi, I’m hitting the exact same problem on a Jetson Orin Nano 8GB and would really appreciate an official answer.

Setup

  • Hardware: Jetson Orin Nano 8GB (GPU compute capability SM 87)
  • JetPack 7.2 / Jetson Linux R39 (rev 2.0)/etc/nv_tegra_release shows # R39 (release), REVISION: 2.0
  • Container: nvcr.io/nvidia/deepstream:8.0-triton-multiarch (DeepStream 8.0.0)
  • Launched with: docker run -it --rm --runtime=nvidia nvcr.io/nvidia/deepstream:8.0-triton-multiarch

Symptom
As soon as nvinfer tries to build a TensorRT engine from ONNX (PeopleNet), it fails and the process segfaults:

ERROR: [TRT]: IBuilder::buildSerializedNetwork: Error Code 9: API Usage Error
(Target GPU SM 87 is not supported by this TensorRT release.
 In checkCurrentSMEnabled at optimizer/common/builderHelpers.cpp:707)
Segmentation fault (core dumped)

The pipeline links fine and nvtracker loads ([NvMultiObjectTracker] Initialized) — it only fails at the TensorRT engine build because the GPU is SM 87 (Orin).

What I found while debugging

  • TensorRT in the container is libnvinfer10 10.13.2.6-1+cuda13.0, and apt-cache policy libnvinfer10 shows it was installed from the SBSA repo: https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2404/sbsa i.e. the server-ARM (SBSA) / dGPU TensorRT build, which appears to have no SM 87 (Orin) kernels.
  • CUDA in the container is cuda-cudart-13-0 13.0.48.
  • I’m already using --runtime=nvidia, but the container’s bundled SBSA TensorRT is what gets used.
  • The DeepStream 8.0 release notes list Jetson support as Jetson Thor only, which seems consistent with the missing SM 87 support.

My questions

  1. Is DeepStream 8.0 supported on Jetson Orin (Nano/NX/AGX) at all, or is its Jetson support limited to Jetson Thor? A clear yes/no would help a lot.
  2. If Orin is supported on DeepStream 8.0, which exact container image tag and/or TensorRT package should I use so that TensorRT includes SM 87 kernels (i.e. not the SBSA build)? Is there a Jetson/L4T-specific DS 8.0 image?
  3. If Orin is not supported on DeepStream 8.0 / JetPack 7.2, what is the recommended supported combination for Orin right now — e.g. JetPack 6.2 + DeepStream 7.1? (DeepStream 7.1 fails on this JP7.2/R39.2 host with GStreamer ABI errors like undefined symbol: g_once_init_enter_pointer, so it seems 7.1 needs JP6.x.)
  4. Is there an ETA for DeepStream Orin support on the JetPack 7.x line, if it’s planned?

Thanks in advance — I just need to know whether to wait for a fix, switch to a supported DeepStream/JetPack combo for Orin, or change hardware.

Please refer to DeepStream compatibility table: Installation — DeepStream documentation

DeepStream has announced that DeepStream 8.0 does not support Jetson Orin serials since the version is released. Please follow the DeepStream platform compatibility exactly.

Thank you for the confirmation.

I checked the DeepStream platform compatibility table. From the table, my understanding is:

For Jetson Orin Nano / Orin Nano Super, the supported DeepStream combination should be:

  • DeepStream: 7.1

  • JetPack: 6.1 GA

  • L4T: 36.4

  • Ubuntu: 22.04

  • CUDA: 12.6

  • cuDNN: 9.3.0

  • TensorRT: 10.3.0.31

  • Docker image: deepstream:7.1

And DeepStream 8.0 is listed for AGX Thor with JetPack 7.0 / L4T 38.2, so it is not expected to support Jetson Orin Nano.

Can you please confirm the exact officially supported combination for Jetson Orin Nano Developer Kit / Orin Nano Super?

Specifically:

  1. Is the correct supported stack for Orin Nano Super:
    JetPack 6.1 GA + L4T 36.4 + DeepStream 7.1 + deepstream:7.1?

  2. Should I downgrade/reflash the current device from JetPack 7.2 / L4T R39.2 to JetPack 6.1 / L4T 36.4 for DeepStream 7.1 support?

  3. Is there currently any supported DeepStream version for Jetson Orin Nano on JetPack 7.x / L4T R38/R39, or is JetPack 6.1 + DeepStream 7.1 the latest supported path for Orin Nano?

  4. For Docker usage on Jetson Orin Nano with JetPack 6.1, should the correct container tag be exactly:
    nvcr.io/nvidia/deepstream:7.1-samples-multiarch
    or should we use another specific Jetson/L4T DeepStream 7.1 tag?

  5. After moving to JetPack 6.1 / L4T 36.4, should the previous nvstreammux / src_bin_muxer plugin ABI errors disappear, since the host JetPack/L4T stack will match DeepStream 7.1?

I want to make sure I use the exact NVIDIA-supported version combination before reflashing the Jetson.

Final response expected which is correct combination of packages and hardware is correct for my current scenario?

this JetPack 7.2: Jetson Software Goes Agentic with Jetson Linux 39.2 and JetPack SDK Downloads and Notes | NVIDIA Developer

both orin and deepstream 8.0 listed
do we expect a fix or support soon?

Hi, @pradeep_prabhu :

Yes.

Yes.

No.

Please refer to Docker Containers — DeepStream documentation

Please pay attention to DeepStream SDK FAQ - Intelligent Video Analytics / DeepStream SDK - NVIDIA Developer Forums

Hi, @mar20122102 :

I think we are talking about DeepStream SDK but not JetPack. We never say JetPack 7.2 does not support Orin platform.

If you are requesting the DeepStream version which support Orin platform, currently the latest version is DeepStream 7.1 + JetPack 6.1/6.2.

The new DeepStream version which supports Orin platforms is under consideration, please wait and keep an eye, there will be announcement in forum when it is available.