Image from Container Registry immediately fails on IoT Edge

Question

Hi,

My account is not yet verified so I can't post images or links but I hope we can solve this somehow.

I followed Quickstart: Deploy your first IoT Edge module to a Linux x64 device tutorial and got it to work.

Then I pulled the tempSensor module and tagged it with a different name. Then I pushed the module to my ACR. I just wanted to test if my ACR works and deployed the renamed image to my edge device. It does get deployed to my edge device but it fails immediately.

In Azure Portal> IoT Hub> IoT Edge> device details window that my renamed module Type=IoT Edge Custom Module, Specified in Deployment=Yes, Reported by Device=Yes, Runtime status=Failed, Exit code=139.

In module details I can see the Image URI is my registry path but the status description is exited, runtime status failed and exit code is 139.

In my edge device the image can be seen with sudo docker images.

sudo iotedge list shows it is Failed (139).

sudo iotedge logs acr-testi (which is my module) it shows:

Unhandled Exception: System.AggregateException: One or more errors occured. (Missing path to certificate file.) ---> System.InvalidOperationException: Missing path to certificate file.

and the log continues but it is too long for me to write. Hopefully I get my account verified so I can post the full log.

Has anyone got an idea how to solve this?

Thanks,
-toto

Answer 1

Now I got my account verified. Here are some screenshots. Anyone got an idea how to fix this?

Answer 2

Anyone?

Answer 3

Hello totomestari,

If your goal is to test if your ACR works, can you please go through the following tutorial?

https://docs.microsoft.com/en-us/azure/iot-edge/tutorial-csharp-module

"Then I pulled the tempSensor module and tagged it with a different name. Then I pushed the module to my ACR."

This is not a supported scenario and something we have tested so far.

Thanks!

Answer 4

I am pretty sure this would work, thanks. My time however with this project came to end and I don't have the Azure resources anymore to try this solution.