Can colima use a bridge network?

[bmwinstead]

Apologies if I get any terminology wrong...

With colima start --network-address I can trivially see the colima VM from my laptop, which is awesome! However, I'd love it if I could have a bridge network or shared IP space that's shared between my laptop and the lima VM.

The use case for this is to support installing MetalLB on a kind cluster and create IP-based load balancers that are visible from the host. I need to be able to have multiple LBs that use the same TCP port on different IPs, and this seems to be the only way to accomplish this. The only other way currently would be to use minikube with a vm driver and those are a little clunky... colima would make this a lot simpler.

Is this possible today? Using a lima override maybe? If not, is it a feasible feature request?

[leotu]

Ref.
#375 (comment)

Ref. Install socket_vmnet
https://lima-vm.io/docs/config/network/#socket_vmnet

[torarnv]

I have the same question. The instructions in #375 (comment) are not clear.

The Lima override in ~/.lima/_config/override.yaml is not picked up by Colima, as Colima seems to use a separate $LIMA_HOME in ~/.colima/_lima/.

Modifying ~/.colima/_lima/_config/override.yaml does "work", in that the change is picked up, but since ~/.colima/_lima/_config/networks.yaml only contains a user-v2 network (https://github.com/abiosoft/colima/blob/9b0809d0ed9ad3ff1e57c405f27324e6298ca04f/embedded/network/networks.yaml) it fails with:

> errors inspecting instance: [field `networks[2].lima` references network "bridged" which is not defined in networks.yaml]

And the networks.yaml can't be edited, as it's overwritten each time Colima starts.

So how is this supposed to work?