[Windows container] debug csharp module failed about iotedgehubdev HOT 11 CLOSED

Incorrect time in containers, plese see moby/moby#37283

from iotedgehubdev.

from iotedgehubdev.

docker 18.06 has port forwarding issue on windows container

from iotedgehubdev.

@czgtest please check this issue again with the latest docker version

from iotedgehubdev.

@adashen this issue still repro on windows-container. prot 53000 and 8883 are not finding by default.
user need to check "Experimental Features" in docker settings, prot 53000 and 8883 are finding when send request ,but breakpoint is not hit

from iotedgehubdev.

by the way, local debug for c# module work well on docker liunx container

from iotedgehubdev.

@czgtest please check the single module debug scenario for csharp module with windows container again. And close the issue if could not reproduce.

from iotedgehubdev.

this issue still repro on windows container, so keep it open

from iotedgehubdev.

switch to amqp it works. It should be the SDK issue on mqtt. Azure/azure-iot-sdk-csharp#574

from iotedgehubdev.

Hi, I'm not able to start iotedgehubdev having docker set with Windows containers (switching to Linux containers it works); I receive the following error trying to start it from cmd:

Network azure-iot-edge-dev is external, skipping
ERROR: Could not start container: af67a255c6ea3474d53fc6092509ce68438d5d4d893aaa0e55d4a5dbd39f3066 : 500 Server Error: Internal Server Error ("failed to create endpoint edgeHubDev on network azure-iot-edge-dev: failed during hnsCallRawResponse: hnsCall failed in Win32: The process cannot access the file because it is being used by another process. (0x20)")

I've tried different workarounds found on other sites (docker/for-win#3171), like excluding some port ranges from reservation performed by Hyper-V, but no way.

from iotedgehubdev.

Hi

Thank you for filing the issue.

We are looking to clean up the reported issues that are obsolete such that our team can focus on the latest issues reported.
As such, we are going to close the issue for now.

If the issue is still blocking or critical to you, please file a new issue and we will do our best to respond as soon as possible.
When you file a new issue, please ensure following additional information are provided.

o If you believe it’s a bug, provide detail repro steps.
o If it’s a feature request, please note as such
o Expected outcome
o Is this a blocking issue?

Thank you,
Azure IoT Developer and Device team

from iotedgehubdev.