Well, I managed to solve it via:
- On the host, inside the project directory, the settings.json file:
"host_ip": "192.168.100.6",
- On the Verdin device, replacing the old IP with the proper one:
torizon@verdin-imx8mm-15400884:~$ cat /etc/docker/daemon.json
{
"insecure-registries" : ["192.168.100.6:5002"]
}
As a result, I was able to run my C hello-world example.
Still, I guess there is some issue on a multi-NIC host scenario. Expected behaviour is that the host “discovery” should be done on a per-subnet basis. If not in the same subnet, then the Torizon automation should at least check the reachability in terms of routing and HTTP connectivity.
If you guys agree with me, you can treat this as a feature request.