Error when starting NVIDIADeepStreamSDK IoT Container. about azure-iot-edge-deepstream-module-with-iot-central HOT 5 CLOSED

Some discussion https://devtalk.nvidia.com/default/topic/1068898/nvidiadeepstreamsdk-iot-image-is-broken-/?offset=5#5414903

from azure-iot-edge-deepstream-module-with-iot-central.

@mitchross,

Can you provide the JetPack version and DeepStream version you are using along with an example of the DeepStream configuration that is causing the error?

Once we have that, we can try to reproduce over here with the same configuration and see if we can get to the root cause.

The NVIDIA forum post mentions that the container may be looking for a previous version of TensorRT which is likely updated in recent Jetpack/DeepStream. If that is the case, the issue might be due to pinning of the DeepStream SDK container to previous sha. This was done to enforce version matching at the time the code was written but could very likely have drifted. If you remove this from the deployment template and instead pull the latest image, does that give a different result?

from azure-iot-edge-deepstream-module-with-iot-central.

JetPack 4.3, Deepstream 4.0.2

removed SHA- same issue

App` run failed

** ERROR: <create_osd_bin:40>: Failed to create 'osd_conv'
**ERROR: <create_osd_bin:114>: create_osd_bin failed ** ERROR: <create_processing_instance:705>: create_processing_instance failed ** ERROR: <create_pipeline:1045>: create_pipeline failed ** ERROR: <main:1096>: Failed to create pipeline Quitting

Gist of the iot deployment manifest and deepstream config -> https://gist.github.com/mitchross/974c6e8e3b73f2b62bd878f5a2c817da

from azure-iot-edge-deepstream-module-with-iot-central.

Perhaps this is a hint -> https://github.com/Azure-Samples/NVIDIA-Deepstream-Azure-IoT-Edge-on-a-NVIDIA-Jetson-Nano/pull/9/files

looks like image name changed?

from azure-iot-edge-deepstream-module-with-iot-central.

@toolboc Issue is resolved with this PR now. #4

from azure-iot-edge-deepstream-module-with-iot-central.