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

Technical Support
, , , ,
4

Persistent Configuration Override Issue

Your issue with VS Code continuously overwriting your network settings is a more severe manifestation of the multi-NIC limitation. Here are specific steps to work around this persistent override behavior:

1. Override Host IP Detection

The extension may be detecting the wrong IP automatically. You can force it to use a specific IP by setting the torizon.overwriteHostIp setting in VS Code’s global settings(1). This prevents the extension from auto-detecting and changing the host IP:

  1. Open VS Code Settings (Ctrl+,)
  2. Search for torizon.overwriteHostIp
  3. Set it to your manual network IP (e.g., “192.168.100.6”)

This setting overrides the automatic IP detection that’s causing your configuration to reset(1).

2. Project-Level Settings Protection

In your project’s .vscode/settings.json, explicitly set these values to prevent overwrites(2):

{
    "torizon_ip": "192.168.x.x",
    "host_ip": "192.168.100.6",
    "torizon_debug_ssh_port": "2230",
    "containers.environment": {
        "DOCKER_HOST": "tcp://192.168.x.x:2375"
    }
}

(2)

3. Docker Daemon Configuration Lock

To prevent the daemon.json from being overwritten on your Verdin device, you can:

  1. Set the file as read-only after configuring it correctly
  2. Create a script that monitors and restores the correct configuration
  3. Ensure the insecure registries include your static IP

4. Connection State Reset

When you encounter the “bad value” error requiring device removal, this typically indicates the extension’s internal state has become corrupted(1). The requirement to restart VS Code suggests the extension isn’t properly cleaning up its connection state.

5. Engineering Mode Behavior

The extension automatically configures Engineering Mode settings each time it connects(3), which includes:

  • Setting up insecure registries
  • Configuring Docker daemon settings
  • Establishing SSH key sharing

This automatic reconfiguration is what’s overwriting your manual settings(3).

6. Workaround Strategy

Given the persistent nature of your issue:

  1. Use the global torizon.overwriteHostIp setting to lock the IP detection
  2. Monitor your daemon.json file and restore it when overwritten
  3. Keep backup copies of your working configuration
  4. Consider using a script to automatically restore correct settings after VS Code startup

Known Limitation Acknowledgment

This behavior represents a more severe case of the known multi-NIC limitation(2). The extension’s automatic reconfiguration is designed for simple network environments and doesn’t handle complex multi-network scenarios gracefully.

The persistent overwriting you’re experiencing suggests the extension is continuously re-detecting network changes and applying what it considers “correct” settings, which conflicts with your manual network setup.

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.