When I run this image ( Microsoft Azure Marketplace ) in a container on a jetson nano the container fails to start with error
“Container fails to run (gst-plugin-scanner:6): GStreamer-WARNING **: 18:47:09.647: Failed to load plugin ‘/usr/lib/aarch64-linux-gnu/gstreamer-1.0/deepstream/libnvdsgst_infer.so’: libnvparsers.so.5: cannot open shared object file: No such file or directory”
Thanks for the reply. Thats defiantly getting me down a path somewhere, however, I am using Microsoft/ Nvidia’s docker image located here Microsoft Azure Marketplace
I don’t think I have any control over setting JetPack4.2.3 + Deepstream 4.0.1… I do follow your logic though…
I have been having the same issue for the last couple of days. I tried using both the latest Jetson Nano Developer Kit SD Card Image (w/ JP 4.3 & Release Date 2019/12/17) and using the SDK Manager to install JetPack 4.3 + Deepstream. Additionally, I confirmed that I using the ARM64 Nvidia Deepstream SDK Azure marketplace module. None of these steps resolved the error.
I can confirm from my testing that using Jetson Nano Developer Kit SD Card Image w/ JP 4.2.3 & Release Date 2019/11/19 resolves this error.
I am not sure what the difference is between these two versions. This issue will most likely need to be resolved by Nvidia since the latest SD Card Image does not work with the latest ARM64 Nvidia Deepstream SDK Azure marketplace module.
For now, I recommend using the older SD Card Image until this issue is resolved by Nvidia. You can download it at the Jetson Download Center. https://developer.nvidia.com/embedded/downloads
The main difference is we upgrade TensorRT package into 6.0 in the JetPack4.3.
This make the docker image cannot find the corresponding v5.0 library and leads to this error.
libnvparsers.so.5: cannot open shared object file: No such file or directory
The container doesn’t support our latest software yet.
I will pass this issue to our internal team and request for an update.
On Jetson, container will try to access the library/driver/software on the Jetson device.
In this container, it required your Nano is setup with JetPack4.2.3 JetPack4.2.2.
So, would you mind to reset your device with JetPack4.2.3 JetPack4.2.2 and give it a try.
This is an option from sdkmanger.
Our internal team is updating the container on Azure into Deepstream 4.0.2, which is compatible to JetPack4.3.
We will update more information once it is done.
JP4.2.3 is removed few weeks ago of sdkmanager
Thanks.
meanwhile, you may use the default DeepStream and use the corresponding text config files to link it with Azure
quote:
Using Azure MQTT protocol adaptor with message broker
=======================================================================
Refer to the README files available under sources/libs/azure_protocol_adaptor
for detailed documentation on prerequisites and usages of azure MQTT protocol
adaptor with the message broker plugin for sending messages to cloud.
Refer to the source code and README of deepstream-test4 available under
sources/apps/sample_apps/deepstream-test4/ to send messages to the cloud.