I’m trying to figure out how to bootstrap a localhost LXD controller, but bridge it to the Ethernet so that other resources on the LAN can access the controller.
The default bootstrap attaches the controller to lxdbr0 which is only accessible from the workstation the controller was bootstrapped on.
Is there a constraint I can pass to achieve this or do I need to do some lxc profile and network wrangling before I bootstrap?
Maybe this can help? Network configuration - LXD - system container manager
And here: https://blog.simos.info/how-to-make-your-lxd-container-get-ip-addresses-from-your-lan/
There’s a Discourse post on setting up bridges for LXD. It is in the context of setting up networking for LXD clustering, but applies just the same for your purpose.
Once you’ve created the bridge, you need to set it as LXD’s network when prompted during LXD init rather than creating a new lxdbr0. It is a function of LXD rather than Juju.
