Azure / Azure/iotedgedev

How to debug module filtermodule created by ioteddev solution init?

Open
#620 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
166
Forks
76
PR merge metrics
No merged PRs in 30d

Description

I am having the same issue trying to debug my module inside the simulator.

The filtermodule doesn't have the Dockerfile.windows-amd64.debug file when created with the iotedgedev solution init
and running dotnet publish --os linux --arch x64 /t:PublishContainer seems to create a production ready container without vsdbg installed

im on a windows machine with linux containers, im actually developing inside the iotedgedev container with the simulator running with the image genearated with dotnet publish --os linux --arch x64 /t:PublishContainer ...

when i f5 i get:

Starting: "docker" exec -i filtermodule sh -c "~/vsdbg/vsdbg --interpreter=vscode"
Error from pipe program 'docker': sh: 1: /home/app/vsdbg/vsdbg: not found
The pipe program 'docker' exited unexpectedly with code 127.

Any ideas?

thank you

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.