We have some devices (actually VMs) running balenaOS in a network that uses the 172.x.x.x address range. We need to be able to access these devices from the 172.17.x.x network, which is also the address range of the internal BalenaOS/Docker network. Is there a way of changing the IP/netmask of the internal network, preferably one that will not be reset when we update BalenaOS?
Hi, we’ve reached you through our paid support system as you pinged us there as well, but for any other users who would read this forum thread, the short answer is that we currently do not support changing the subnet for the containers to a different value than 172.17.x.x.
Thanks,
Zahari