However, when I run incus network ls, it shows that the newly created bridge is not managed by Incus. I also noticed that the interface for this bridge needs to be brought up manually each time.
Do I need to create an Incus-managed bridge instead to avoid any issues? What is considered best practice when bridging a LAN network for Incus containers/VMs?
It’s impossible to create an incus managed bridge network that can access LAN dhcp server. Because all incus managed bridges are managed by incus managed dnsmasq.
How? Please post your config.
No need, you already have an incusbr0, I guess.
Just use a linux/ovs bridge will be ok. If you feel brave you cn try dpdk+ovs. Or you just use macvlan.
Incus in general can manage private networks, using NAT networking. Those instances (containers and VMs) will be able to have access to your LAN and the Internet. When I say access, it means that you can make network connections from your instances to the system on your LAN and the Internet. However, your instances will not be able to get an IP address from your LAN.
If you want your containers to get an IP address from your LAN with _bridged networking_, then you need to create a suitable network interface externally, that is, on your host.
Therefore, as @catfish wrote, Incus cannot manage a network interface that will be used for bridged networking (i.e. the containers get an IP address from the LAN).
As you may have noticed in my blog post, it’s somewhat tricky how to manage the networking of the host so that you create a proper bridge network interface. Depending on what Linux distribution (actually, what network stack) is running on the host, you would need a corresponding tutorial. Various cases include NetworkManager, netplan, ifupdown, etc.