Stuck getting single nic network configured in cluster

i’m admitting defeat, i cannot figure out what i’m missing/mis-understanding on getting the network initially setup in a cluster.

I’m completely new to incus and deploying on 3 raspberrypi’s. Currently using the Incus webUI to config things.

The docs for cluster network appear to be a bit anemic with how to configure for various scenarios.

I’m aiming to get my instances to obtain an IP from my existing LAN DHCP server. I beleive i need the macvlan type for this.

I’m also aiming to use one physical NIC for all traffic on both the instances and the host.

Unfortuantely i haven’t got very far with this - hour of searching for a solution and all i’ve really found is that bridge works as far as instance > host, but is not allowing traffic past the host and onto the LAN network/internet connectivity. I beleive this is because it’s an ‘unmanaged’ issue with eth0 where incus webUI fails to add the parent physical NIC, so there’s no network path out of the host.

for this Bridge type, i’ve attempting to remove the eth0 from NetworkManager and configure within incus but i’ve had even less luck with that as i can’t get the hosts IP back on to allow cluster comm’s again.

:person_facepalming: turned out it was a docker conflict (yes, i saw the note in the incus docs too!). I disabled docker services on the first node, but not the other 2.

bridge and macvlan now working as expected!

1 Like