Open rajaasokan opened 2 years ago
Hi @rajaasokan
IoTEdgeHubDev is an Azure IoT Edge (specifically $EdgeHub module) simulator which handles the message routing from the custom module(s).
The issue you described does not look like it is related to IoTEdgeHubDev itself. I assume the problem you are encoutering also occurs on the physical device or VM which runs IoT Edge runtime as well. Please let us know if you think otherwise.
Having said that, there are several reports on Stackoverflow on the issue which is related to socket connection that you might want to reference.
https://stackoverflow.com/search?q=can+not+assign+requested+address+python
Hi @konichi3 Thanks for the response.
The problem we are encountering only occurs when we use a compute instance from Azure ML as development environment. It works without error on a physical device or any other VMs.
We are using Azure ML compute instance as a development environment for IoT Edge solutions.
We are trying to get our development environment with iotedgedevhub in running in an Azure ML Compute Instance (because it is already used extensively in our development processes, it offers GPU options we need for our use case and the integration of VS Code is superb).
Unfortunately when we try to debug our solution (which works on many other devices we tested them on) we receive an error: 'Cannot assign request address'. We have the feeling that problem is either Docker Environment or Networking related but are struggling to find the reason.
Logs from module: