Some sort of update to VSC is causing it to lose my default device

Technical Support
, , , ,
2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

Multi-NIC Environment Configuration Issues

Your issue appears to be related to a known limitation with the Torizon IDE Extension in multi-NIC environments. Based on the available documentation, here are the key solutions:

1. Manual Host IP Configuration

The Torizon IDE Extension can struggle with automatic IP detection when multiple network interfaces are present(1). You can manually configure the host IP in your project’s settings.json file(1):

"host_ip": "192.168.100.6",

(1)

2. Engineering Mode Configuration

When the Torizon IDE Extension connects to a device, it sets up Engineering Mode which includes configuring insecure registries(2). The extension automatically adds your development PC’s IP as an insecure container registry in /etc/docker/daemon.json(2):

{
	"insecure-registries" : ["<your development PC's IP>"]
}

(2)

3. Manual Registry Configuration

To prevent the extension from overwriting your registry settings, you may need to manually maintain the daemon.json file on your Verdin device(1):

{
   "insecure-registries" : ["192.168.100.6:5002"]
}

(1)

4. Network Connectivity Verification

Ensure proper network connectivity between your development machine and the Verdin board(3):

  • Verify both devices can communicate with each other
  • Check that port 2375 (Docker daemon) is accessible(3)
  • Confirm your local registry port (typically 5002) is accessible from the board(3)

5. Docker Configuration Considerations

Since you’re using Docker Desktop with WSL2, ensure you’re not running both Docker Desktop and Docker Engine simultaneously, as this can cause conflicts with the VSCode extension(3). The documentation recommends using Docker Engine in WSL2 rather than Docker Desktop when possible(4).

Known Limitation

The multi-NIC scenario you’re experiencing is a recognized limitation of the Torizon IDE Extension(1). The expected behavior should include per-subnet discovery and reachability checking, but this functionality is not currently implemented(1).

Workaround Summary

  1. Set the host_ip manually in your project’s settings.json
  2. Manually configure the insecure registries on your Verdin device
  3. Monitor and manually correct the daemon.json when the extension overwrites it
  4. Ensure consistent network connectivity between your development machine and target device

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.