I currently run anbox cloud on google VMs and they can tolerate an external ip change when it does down and up. However, I want to run on spot servers (cheaper). I persist the HD when the server is killed, then reattach it to the exact same device and update the IPs but it fails to start. Wondering what the restrictions are that are preventing it from starting? The logs complain about not being able to determine a listening ip but I’ve updated the IPs before and that doesn’t seem to be a problem.
Hey @reza666,
generally speaking the private IP address your machine has assigned must remain the same as the configuration of the instance is bound to it. If the private IP address stays the same, the public can change and you can adjust the appliance configuration to fit a newly assigned one. Have a look at https://documentation.ubuntu.com/anbox-cloud/reference/appliance-configuration/
What you need to do is
$ sudo anbox-cloud-appliance config set network.public_address=<new public address>
$ sudo anbox-cloud-appliance config set network.location=<new DNS name, if you have one>
You can also set both in a single command. When set the appliance will restart and apply the new values to its internal configuration.
Let us know if there is anything else we can help with!