AzureIoT-CoreUtils
azedge iothub edge azure
Some PowerShell scripts for setting up containers on Win 10 IoT-Core: In particular, setting installing and uninstaling requires a local PowerShell script; that is, one copied to the device.
See the GitHub Repository: djaus2/AzureIoT-CoreUtils
Nb: On Windows 10 IoT-Core you need a 64 bit version of the OS and so won’t current run Containers on the RPI. I am using a MinnowBoardMax. I have run the Az Edge container examples on Raspberry PI running Raspbian. They might work on an NXP IOT-Core (ARM64) device ??
When deploying Azure IoTEdge Containers to a Windows 10 IoT-Core device, the Azure cLI commands need to be a little different to those stated in some of the Azure IoT Hub documentation. In particular, setting installing and uninstaling requires a local PowerShell script; that is, one copied to the device. I have been working through the tutorials such as:
- Quickstart: Deploy your first IoT Edge module from the Azure portal to a Windows device - preview
- Tutorial: Develop a C# IoT Edge module and deploy to your simulated device
I found that in “Install and start the IoT Edge runtime/Download and install the IoT Edge service”, Step 2 doesn’t work if targeting an IoT-Core device. The following is the Step 2 comamnd that won’t work:
. {Invoke-WebRequest -useb aka.ms/iotedge-win} | Invoke-Expression; `
Install-SecurityDaemon -Manual -ContainerOs Windows
There was some discussion of this issue with a workaround presented. The PowerShell scripts presented here are a formal encapsulation of that solution.
Another issue has surfaced: If you reboot an IoT-Core device running Az IoT Edge, the containers don’t restart, except, maybe, the Agent. From Feedback:
After installation, all runs fine. But after every reboot the edgeAgent does not find its network anymore and thus fails to start the modules. It looks like the “azure-iot-edge” network is recreated on every docker restart with a different id. But the edge containers do not get notified about this by the daemon.
After reboot just run the restart-rm.ps1* script and it will re-pull those containers. NB: The old images are still on the device so some cleanup may be required. It is expected that this issue is to be addressed in an updated image.
Some of these issues may have been resolved in later releases of teh Az IoTHub Edge software.
Topic | Subtopic | |
Next: > | HSQLDB.Net | .Net interface for HSQLDB Database |
< Prev: | ClickOnce Hosting on Azure | |
This Category Links | ||
Category: | Az IoT Hub + Edge Index: | Az IoT Hub + Edge |
Next: > | A Brief History in IoTime |