From the log in your last comment, there was no any error printing. there was only some logs of Triton starting. Do you mean if starting the docker with method in the guide, nvidia-smi and deepstream-test1 work well every time? if so, please simplify the custom docker start method to narrow down this issue. Here is a sample.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| WARNING: erroneous pipeline: no element "nvinfer" On nvcr.io/nvidia/deepstream:6.1-devel Docker | 5 | 650 | June 27, 2022 | |
| Device '/dev/nvidia0' failed during initialization | 12 | 1323 | April 18, 2023 | |
| DeepStream 5.1 Docker, deepstream-test3.py, gst-stream-error-quark: Internal data stream error | 4 | 376 | March 25, 2024 | |
| Fail to use the Docker Deepstream 7.1 Dev | 5 | 218 | January 16, 2025 | |
| When i run deepstream sample, i'm getting following error message:- | 16 | 1368 | July 29, 2022 | |
| deepstream for tesla in docker | 8 | 1855 | June 5, 2018 | |
| Nvcr.io/nvidia/deepstream-l4t:5.0.1-20.09-base run error | 4 | 478 | October 12, 2021 | |
| Deepstream 7.1 in wsl2 throws cuda failed to initialize error | 3 | 119 | December 26, 2024 | |
| Deepstream docker nvidia | 2 | 633 | January 25, 2022 | |
| No such element or plugin 'nvstreammux' on deepstream:5.1-21.02-devel docker | 2 | 1136 | October 12, 2021 |