Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Connect container to azure-iot-edge and local docker network.
See original GitHub issueHello. We are trying to deploy a docker image to an Azure IoTEdge device.
If we do not specify any networking in Container Create options in Deployment, it automatically connects to the azure-iot-edge network. However, we need our container to also be connected to another network local_network_name in addition to azure-iot-edge network.
If we try to specify both networks in Container Create options our container fails to start because azure-iot-edge network is non Attachable. We have been able to get it running in the lab by manually connecting our container to the azure-iot-edge network after it has been created.
Our container has to be able to communicate to both EdgeHub and local containers in order to function. Is there a way we can resolve this issue?
Issue Analytics
- State:
- Created a year ago
- Comments:12 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
that is essentially what we have been doing. but we need this to happen without manual intervention
alternatively, if there is some other way we can get our image to be able to open the connection it uses to register direct method handlers without being on the azure-iot-edge network, that would also be acceptable