LXD Container not accessible from LAN

[tomp (Thomas Parrott)]

@girish.meena is this related to your other case?

Network unreachable after adding new bridged interface

Another option you could use if you do not need the container to talk to the host is to use the ipvlan type nic device, as that allows statically configured IPs from LXD and will appear directly onto the network by sharing the host’s MAC address: https://linuxcontainers.org/lxd/docs/master/containers#nictype-ipvlan

If so, check that your Windows 10 VM is allowing multiple MAC addresses on its own bridged interface and that the VM’s nic device is set to promiscuous mode to allow it to receive packets that are not for its own MAC address. Otherwise they will not get into the VM to be accessible to LXD.

This might be another benefit of using the ipvlan nic type I mentioned in the other thread, as it will share the host’s MAC address.