VS Code AppoloX extension: Wrong host_ip leading to connection problems

I’m evaluation the Colibri iMX8DX 1GB with the goal to migrate our C# application currently running on a Colibri T30 with WinCE. I loaded VSCode with the new AppoloX extension.

When creating a new C# project from scratch, the host_ip setting in settings.json is incorrectly set to an IP from the wrong adapter:

settings.json

{
  "torizon_psswd": "xyz",
  "torizon_login": "torizon",
  "torizon_ip": "192.168.1.202",
  "host_ip": "169.254.145.175",
  "torizon_workspace": "${workspaceFolder}",
...
}

The correct host IP should be 192.168.1.226. The 169.x is an autoconfig IP from another ethernet adapter (not on the same network).

ipconfig output:

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : xxxx
   Link-local IPv6 Address . . . . . : fe80::dfca:959f:d9a7:38d0%7
   IPv4 Address. . . . . . . . . . . : 192.168.1.226
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1

Ethernet adapter Ethernet 2:

   Connection-specific DNS Suffix  . :
   Autoconfiguration IPv4 Address. . : 169.254.145.175
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :

I can manually change it to the right one (192.168.1.226), however this leads to another error when the module tries to pull the docker image from the host:


Warning: Permanently added '192.168.1.202' (ED25519) to the list of known hosts.
The DOCKER_LOGIN variable is not set. Defaulting to a blank string.
Pulling torizontest2-debug ... 
Pulling torizontest2-debug ... error

ERROR: for torizontest2-debug  Get "https://192.168.1.226:5002/v2/": http: server gave HTTP response to HTTPS client
Get "https://192.168.1.226:5002/v2/": http: server gave HTTP response to HTTPS client

Google pointed me to add "insecure-registries" : ["192.168.1.226:5002"] to my Docker Desktop instance, but I realised this error came from the module and not my host. I manually edited /etc/docker/daemon.json and it now work.

Is there a way to avoid this problem? When is the wrong IP fetched in the process?

Greetings @etgauth,

We’re running this by our IDE extensions team to see if they have an idea around this behavior you are seeing.

Best Regards,
Jeremias

I think it’s more or less the same issue that I saw here