Oh that's right, Vagrant on VMware Fusion doesn't support customised networks on OSX anymore

great

thanks Hashicorp and Broadcom, everything about this sucks now

*sad, annoyed noises*

Maybe it's just arm64? or maybe it's Fusion as a whole? Who fucking knows. Vagrant is abandonware at this point anyway, I really do need to move on.

With native containerisation on macOS 26, hopefully, *hopefully*, everything stops sucking quite so much for trying to do container-based development on OSX...

Well, I am now sorta hacking together a `justfile` that provides some of the commands I expect to have for development around VMs, since Incus does support VMs and not just containers.

Does seem like I'm about to write an `incusfile` file format so I can make system declarations obvious in a way they are currently not.

I am in a maze of twisty yaks, all shaped like Vagrant.

It feels *slightly* ridiculous to be using `just` to do this but it does make for a very easy-to-use interface for defining commands to be run.

Arguably using `click` in Python and directly querying the Incus API would be a better design but when has bad design ever stopped me?

oh look am I writing bash inside of my justfile to use yq to parse a yaml file I just defined so I can do things like `just status` and have it go check if the instances I've defined were created

I am

it is somewhat cursed