After updating LXD, I can no longer set up the proxy. It says that the virtual machine needs a static IP. When I first installed LXD, I didn’t need to configure anything; I would just add the ports and didn’t have to do anything else as shown in the following image. But now it doesn’t work.
If I use the terminal and set a static IP with the LXD command, I can do the configuration, but SSH access is very limited, and it’s not practical to do this every time I set up a machine. Is there a more practical solution?
I am using the official images available in LXD.
Also, it works fine with containers, but it’s only with virtual machines that this issue occurs.
VMs require NAT mode because they dont use a proxy process but rather use NAT rules to direct traffic from the host to the VM.
Because of this the listen address must be a specific IP (not the wildcard address 0.0.0.0 you’ve specified) and the connect address must be a static IP inside the VM.
In order to assign a static IP to the VM, the VM’s eth0 NIC device should have an ipv4.address setting specified, so that LXD creates a static DHCP reservation.
This behaviour isn’t new. Perhaps you were configuring a container before, as containers support more flexible options.
Thank you for the answer. What was happening earlier is that I’m using an Nginx proxy in front of that service, and the Nginx proxy is running in a container where this configuration can be adjusted, I just forgot about that detail.
Is it possible to make the default DHCP configuration define static IPs on lease? Can I change that through the web UI, or is it only possible via CLI?
