Torizon IDE extension: torizon.overwriteHostIp ignored in VS Code multi-root workspace on WSL

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.

Addressing torizon.overwriteHostIp in Multi-Root Workspaces

Based on the documentation and community discussions, here’s what I found regarding your issue:

Understanding torizon.overwriteHostIp

According to the official documentation, torizon.overwriteHostIp is designed to override the automatically detected IP address(1). The documentation states: “The IP address set here will overwrite the IP address set automatically into host_ip, from project .vscode/settings.json. Use it as fallback if the automatic IP address set is getting it from the wrong interface for example.”(1)

Known Multi-NIC and WSL Issues

Community reports indicate similar issues in multi-NIC environments and WSL scenarios(2)(3). In one case, a user experienced the extension incorrectly assigning 169.254.201.164 instead of the correct IP(2). Another user working on WSL with multiple network interfaces found that the extension was selecting the wrong interface IP(3).

Recommended Solutions

Based on the community discussions, here are the steps that have worked for others:

  1. Set host_ip directly in the project’s .vscode/settings.json(3):

    "host_ip": "192.168.x.x"

    This approach bypasses the automatic detection entirely.

  2. Update the Docker daemon configuration on the target device(3):
    On your Verdin iMX8M Plus, edit /etc/docker/daemon.json:

    {
   "insecure-registries" : ["<your-new-host-ip>:5002"]
}

    Then restart the Docker daemon on the board.

  3. Verify network interfaces: Run ip addr show on both your WSL host and the target to confirm which interfaces are active and their assigned IPs(2).

Answers to Your Questions

  1. Multi-root workspace support: The documentation doesn’t explicitly confirm multi-root workspace support for torizon.overwriteHostIp. The setting appears designed for single-project scenarios.

  2. Configuration scope: For WSL environments, the extension should read from the WSL remote settings, but multi-NIC scenarios are a known limitation(3).

  3. Evaluation timing: The host_ip value is set automatically by the extension when you configure your default device(1).

  4. Cached values: Yes, the host_ip in .vscode/settings.json persists until explicitly changed or the device is reconfigured.

  5. Workaround: Directly editing host_ip in .vscode/settings.json for each project folder in your multi-root workspace is currently the most reliable approach(3).

Additional Note

This is a known limitation of the extension in multi-NIC and complex network environments(3). The development team is aware of these scenarios.

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.