Hi Steve,
I understand now - you need to enable remote Docker daemon access so the VS Code Torizon extension can connect for debugging. The Docker daemon on Torizon OS runs locally by default and doesn’t expose the TCP port 2375 for remote connections(1).
Enabling Remote Docker Access
To enable remote Docker daemon access for debugging, you need to modify the Docker daemon configuration on your Verdin iMX8M Plus device.
1. Modify Docker Daemon Configuration
SSH into your device and edit the /etc/docker/daemon.json file to enable TCP access:
{
"hosts": ["unix:///var/run/docker.sock", "tcp://0.0.0.0:2375"],
"registry-mirrors" : ["10.40.100.6:5002"]
}
Note: I included your existing insecure registry configuration that was shown in your docker info output.
2. Create Docker Service Override
Since systemd manages the Docker service, you need to create a service override to prevent conflicts with the hosts configuration:
# mkdir -p /etc/systemd/system/docker.service.d
# cat > /etc/systemd/system/docker.service.d/override.conf << EOF
[Service]
ExecStart=
ExecStart=/usr/bin/dockerd
EOF
3. Restart Docker Service
Apply the changes by reloading systemd and restarting Docker(1):
# systemctl daemon-reload
# systemctl restart docker
4. Verify Remote Access
Check that Docker is now listening on port 2375:
# netstat -tlnp | grep 2375
You should see Docker listening on 0.0.0.0:2375.
Security Considerations
Warning: This configuration exposes Docker daemon without authentication. Only use this for development/debugging purposes and ensure your network is secure(2).
For production environments, consider using TLS authentication or restricting access to specific IP addresses.
VS Code Extension Connection
Once the Docker daemon is accessible remotely:
- Remove and re-add your device in the VS Code Torizon extension
- Set the device as default
- Try your debug build - the extension should now be able to connect to
tcp://10.40.100.5:2375
Alternative: Local Registry Cache
If you’re still having issues with container pulls, you can also set up a local registry cache(3). Your daemon.json already shows an insecure registry at 10.40.100.6:5002, which suggests you may have this partially configured.
This should resolve the connection issue and allow you to debug your application through the VS Code Torizon extension.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
