Anton Els

Agree, this would be a great option to have as had same issue as @Gerharddc Using custom role was not option as this plugin then does not work as it...

What might be good is cleanup and restart - and yes, restart sounds not needed, but if you had a system running for a while, and updated software etc -...

tried updating colima to latest as well as QEMU to latest, but no difference, also tried latest k3s ("v1.26.3+k3s1") , still same: ``` colima version HEAD-65ee3d2 git commit: 65ee3d284b81bfebc09783f5e35a186584aa4bc1 ```...

I have tried using "--vm-type vz" but same issue. The "col0" interface inside the VM does not seem to get assigned. Example using default profile: ``` $ colima start -c4...

And as it does not seem to finish properly the kubectl context is not set, and I cannot get a colima status to work. ``` $ docker context list NAME...

I am not switching an existing VM, I am deleting and recreating these VMs. I have used: colima start......... Then I use: colima delete -f ...... I am also using...

Thank you, this is really strange one. I have used colima mainly with **QEMU** on the M1 as that worked really well and I had issues with the "**vz"** a...

Ok, quick update, I saw this in the k3s log ``` ... time="2023-04-03T04:17:04Z" level=info msg="Found ip fd66:cebe:fcc3:1333:5055:55ff:fea2:ea9d from iface col0" ... ``` which made me think that IPV6 is causing...

Just another update, tried on another Mac 13.3 update on M1 and even if we set the network to `Link-Local only` and reboot Mac, still seem to have issue where...

I have been looking at this more and I think this issue discussed here is related - https://github.com/lima-vm/lima/issues/1259 It looks like bootp - dhcp is not working properly as it...