Subnet Mask Issues for deploying docker images from Torizon IDE

[vmetodiev]

Hi @belangen ,

Well, a few hours ago I had the “opposite issue” - the Torizon IDE discovery bound the socket to an IP address from a different subnet, below is my post:

TorizonCore - example C project

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…

Can you share some outputs from commands like netstat or lsof, to be able to identify the registry socket binding?

Also, from my observations, it binds to a specific IP address, without checking the subnet mask. So, changing from /24 to /16 or whatever else should be absolutely transparent from software point of view, as long as you have OSI Layer 3 reachability between the endpoints.