wago / azure-iot-edge Goto Github PK

Based on the documentation we succeed to deploy the azure-iot-edge runtime on the WAGO device connected it our Azure IoTHub and successfully deployed some modules on the device.

But when we try to connect to external device via a TCP/UDP connection from a IoT Edge module running on the Wago device we're not able to access the external device. The external device is in the same ip segment as the host network of the Wago device. And also if we deploy an container on the host network of the docker instance we are able to access the external device.

So we assume that we cannot access the external device because all the containers for the IoT Edge modules are created within a separate azure-iot-edge docker network and probably the routing is not configured properly. Do you perhaps have some guidance on how to approach this scenario? And is this even a supported scenario from this device?

With the newest version the container starts, but the docker-entrypoint.sh fails with "docker not found" in line 20.

me@randomhost:~ $ sudo docker run --name azure-iot-edge-runtime -v /var/run/docker.sock:/var/run/docker.sock -v /config:/config wagoautomation/azure-iot-edge
azure-iot-edge
b5e5b8a864df
/docker-entrypoint.sh: line 20: docker: command not found
/docker-entrypoint.sh: line 21: docker: command not found
Device "eth1" does not exist.
...

To have docker available from inside the container, add -v /usr/bin/docker:/usr/bin/docker to the mapped volumes.