Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Windows container] debug csharp module failed #62

Closed
czgtest opened this issue Aug 1, 2018 · 11 comments
Closed

[Windows container] debug csharp module failed #62

czgtest opened this issue Aug 1, 2018 · 11 comments

Comments

@czgtest
Copy link

czgtest commented Aug 1, 2018

repro on :
windows10
docker * windows container
Csharp local module testing

test case : Start edgehub for local module testing (csharp)
Run “Iotedgehubdev modulecred”
Copy the output env to the csharp launch debug configuration in vscode
Run “iotedgehubdev start -i ”
Make sure it is successfully started and “curl” message shows up
In vscode F5 to start the debugger.
verify the error in screenshot.

image
docker logs edgeHubDev
image

@czgtest
Copy link
Author

czgtest commented Aug 3, 2018

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

@czgtest
Copy link
Author

czgtest commented Aug 3, 2018

image

@adashen
Copy link
Contributor

adashen commented Aug 9, 2018

docker 18.06 has port forwarding issue on windows container

@adashen
Copy link
Contributor

adashen commented Mar 28, 2019

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

@czgtest
Copy link
Author

czgtest commented Mar 29, 2019

@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

image

image

@czgtest czgtest assigned adashen and unassigned czgtest Mar 29, 2019
@czgtest
Copy link
Author

czgtest commented Mar 29, 2019

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

@adashen adashen assigned czgtest and unassigned adashen Dec 12, 2019
@adashen
Copy link
Contributor

adashen commented Dec 12, 2019

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

@czgtest
Copy link
Author

czgtest commented Dec 16, 2019

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

@adashen
Copy link
Contributor

adashen commented Dec 16, 2019

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

@alesomas
Copy link

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.

@konichi3
Copy link
Collaborator

konichi3 commented Jan 9, 2021

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

@konichi3 konichi3 closed this as completed Jan 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants