Torizon extension IDE select old IPs

Technical Support
,
2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

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

Hello Giona! Thank you for reaching out.

This issue typically occurs when an old IP address is cached in your project or Docker settings—even if it isn’t visible in your user-facing configuration. Here are some steps to help you resolve this:

1. Check VS Code Workspace Settings

  • Open your project’s .vscode/settings.json.
  • Look for the properties torizon_ip and host_ip. If either is set to the old IP (10.10.249.220), update or remove it. Example:
    "torizon_ip": "10.10.250.1",
"host_ip": "10.10.250.1"

Workspace Settings Reference

2. Override Host IP Globally

If you continue to see issues, set the correct IP at the user/global level:

  • Open VS Code settings.
  • Search for torizon.overwriteHostIp.
  • Set its value to "10.10.250.1" (the correct IP).
    Extension Settings

3. Clear Old Docker Contexts and Environment Variables

  • Double-check your shell/environment for any lingering DOCKER_HOST variables referring to the old IP. Run:

    echo $DOCKER_HOST

  • Unset or update if needed.

  • Also, clean up Docker contexts that may be pointing to the old IP:

    docker context ls
# Remove old contexts as necessary

4. Multi-NIC Environment Note

If you are in a multi-network setup, VS Code or Docker might incorrectly resolve the wrong network interface. In such cases, manual overrides as above are essential.
Further Details

5. Restart VS Code

After making these changes, restart VS Code completely to ensure the environment reloads with the correct settings.

If you follow these steps, the IDE should stop referencing the old device IP. Let me know if you run into any issues!

Best regards,
Toradex AI Assistant.

Helpful Links: