Docker insecure-registries entry is wrong on device

Technical Support
, , ,
1

Hello,

yesterday I did a fresh install of VSCode and Torizon IDE 3.6.0 with Torizon WSL 2 on Windows 11.

After connecting to device I checked /etc/docker/daemon.json on device. As meantioned in an older post, the IP under “unsecure-registries” was wrong.
I removed and added the device again and set to default, but the IP stays wrong. I corrected the entry by myself.

Is Toradex aware of this issue?
Here is my old post:

Regards
Lars

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.

I’m sorry, but I don’t have specific documentation about this known issue with the Torizon IDE Extension not updating the insecure-registries IP address in /etc/docker/daemon.json when the network changes.

However, based on the documentation, when connecting to a device, the Torizon IDE Extension sets up Engineering Mode, which includes enabling your development PC’s IP as an insecure container registry(1). This configuration is added to /etc/docker/daemon.json on the device(1).

Since you’re experiencing this issue consistently after a fresh VSCode and Torizon IDE 3.6.0 installation, and the problem persists even after removing and re-adding the device, I recommend:

  1. Check your network configuration: Ensure your development PC and target device are on the same network(1)
  2. Verify the IP detection: Check what IP address your development PC is using on the network interface connected to the device
  3. Manual workaround: As you’ve already done, manually correct the entry in /etc/docker/daemon.json on the device
  4. Report the issue: Since this appears to be a recurring problem with the IDE Extension, consider reporting it through the Toradex Community with detailed information about your network setup (WSL2, Windows 11, network adapter configuration)

The community discussions you referenced suggest this may be related to how the IDE Extension detects the development PC’s IP address, particularly in WSL2 environments where network configuration can be more complex(2)(3).

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.

3

The device and PC are in the same local network.
Device 192.168.179.12/24
PC 192.168.179.13/24

Output on IDE:
[07-09 08:00:47.625] Checking host ip sanity …
[07-09 08:00:48.884] Host ip is OK
[07-09 08:00:48.889] Device 192.168.179.12 set as Docker Host

IP in “unsecure-entries” on the device is set to: 192.168.179.3
There is not network device on this IP.

WSL vEthernet adapter is 172.22.176.1.

A VPN connections runs on an adapter with IP 192.168.113.3/24

4

Thank you for providing those details. This clarifies the issue — the Torizon IDE Extension is incorrectly detecting your host IP as 192.168.179.3 instead of your actual PC IP 192.168.179.13.

Based on the documentation, there is a known workaround for this exact scenario. The Torizon IDE Extension provides a setting to manually override the host IP detection(1).

Solution

You can set the torizon.overwriteHostIp setting in VS Code global settings to specify the correct IP address:

  1. Open VS Code Settings (File → Preferences → Settings)
  2. Search for torizon.overwriteHostIp
  3. Set it to your correct PC IP: 192.168.179.13

According to the troubleshooting documentation: “This can happen when the host is using some VPN or other network configurations that may change the IP address of the host, or have multiple interfaces”(1). Your setup with a VPN connection on 192.168.113.3/24 and WSL vEthernet adapter on 172.22.176.1 is exactly the type of multi-interface configuration that can cause this issue.

The documentation specifically states: “To workaround this issue, you can set the torizon.overwriteHostIp setting in the VS Code global settings to the correct IP address from the main interface that the host is using”(1).

After setting this configuration, try reconnecting to your device. The extension should now use 192.168.179.13 when configuring the insecure-registries entry in /etc/docker/daemon.json on your 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.

5

I set the VSCode setting torizon.overwriteHostIp to 192.168.179.13 and restart VSCode.
But reconnection (clear default, remove device, connect device, set default) does not put the host ip into the “insecure-registries” setting on device.

6

Greetings @Lars.ceta,

But reconnection (clear default, remove device, connect device, set default) does not put the host ip into the “insecure-registries” setting on device.

Could you try deleting the /etc/docker/daemon.json on the device before reconnecting. Maybe it’s the case that the old file isn’t being overridden.

Also do you see anywhere else in the extension that the incorrect IP address is being used? Or is it just in daemon.json where the iP address is incorrect?

Best Regards,
Jeremias

7

Hi @jeremias.tx ,

The file was deleted. Reconnecting does not create the file. It’s gone.

I checked the files in .vscode and did not find a problem.

Regards
Lars

8

The file was deleted. Reconnecting does not create the file. It’s gone.

That’s very strange, the file should be created on adding the device to the extension. Let me run this by our extensions team if there is a possible bug somewhere.

Best Regards,
Jeremias

9

We’ve been unable to reproduce this issue on our end. In every case the /etc/docker/daemon.json file gets recreated when a device is added. So it’s strange that it does not get recreated on your setup.

Could you try to reproduce again on your side, but this time share the output of the internal logs during the process. To view the internal logs see the documentation here: Troubleshooting | Toradex Developer Center

Best Regards,
Jeremias