Jan Dubois

> It looks like it impacts hosts that have 16 response entries in them. This may be a bug in the host resolver: it always truncates responses to fit into...

> I will dig around a bit to see if there is a way out. I don't think so, these are hard-coded constants in the lima sources: https://github.com/lima-vm/lima/blob/master/pkg/qemu/const/const.go Please file...

A workaround would be to forward the registry to your host, and then access it via `host.docker.internal` (see #318), but you will have to setup the forwarding yourself.

This was supposed to be fixed in Lima with https://github.com/lima-vm/lima/pull/490. Could you please file an issue against Lima, with the Lima version? While the Lima-internal "fix" has a more coarse...

I'm not convinced the differences between glibc and musl are the root cause here; unless colima does something different, there should be only a single nameserver in `/etc/resolv.conf`, and it...

Typically there is a new lima release shortly after any nerdctl release, so all you have to do is update lima once it is out. If you want to upgrade...

> If you want to upgrade nerdctl before, then the best way is probably to create a `$HOME/.lima/_config/override.yaml` file: Don't forget to remove/edit the override once you update `lima`; otherwise...

I just double-checked, and lima 0.8.0 is available on brew, and uses nerdctl 0.15.0, so upgrading lima and restarting your VM should be all you need.

> I will also consider adding a flag to accommodate additional provision scripts. Not sure why you would need a flag; any provisioning scripts from `override.yaml` will be added before...

@abiosoft I have not checked if you have implemented support for `LIMA_HOME` now, but it would be useful because default/override settings affect all instances under the same `LIMA_HOME` directory. So...