Stuck in Network azure-iot-edge-dev is external, skipping

This is a generic error that is thrown for a variety of reasons. Possible causes can be:

• Proxy blocking pulling images of edgeHub and edgeAgent
• A problem in the deployment.template.json (or debug template), e.g. missing brackets
• Ports of edgeHub that are in use
• Docker configured for Windows containers when targeting Linux or visa-versa

The Build output or IoT hub output in Visual Studio usually gives a bit more information.

Do you know how can I get more logs and/or resolve this problem ?

Are you trying to debug/simulate it locally on windows 10 machine?

When you need to gather logs from an IoT Edge device, the most convenient way is to use the support-bundle command. By default, this command collects module, IoT Edge security manager and container engine logs, iotedge check JSON output, and other useful debug information. It compresses them into a single file for easy sharing. The support-bundle command is available in release 1.0.9 and later.

Run the support-bundle command with the --since flag to specify how long from the past you want to get logs. For example 6h will get logs since the last six hours, 6d since the last six days, 6m since the last six minutes and so on. Include the --help flag to see a complete list of options.

sudo iotedge support-bundle --since 6h

By default, the support-bundle command creates a zip file called support_bundle.zip in the directory where the command is called. Use the flag --output to specify a different path or file name for the output.

Incase if you are looking to debug the modules locally on VS2019, VS Code below documentations will be useful.

Use Visual Studio 2019 to develop and debug modules for Azure IoT Edge and Use Visual Studio Code to develop and debug modules for Azure IoT Edge

Please share the complete logs if the above doesn't help.

I have this issue when trying to start a project from within Visual Studio when it's not running in administrator mode. I always forget and end up with this error. Same goes for if I run "iotedgehubdev.exe setup" from a command prompt. It only works when the command prompt is running in administrator mode.