feat: support Lima VMs iptables rules

[night0wl]

New Features:

• Adds support for Lima-based VM by added a necessary iptables rule

Caveats:

• For Colima, still need to manually symlink /var/run/docker.sock

TODO:

• Update documentation

[gregnr]

Fantastic work @night0wl! Confirming regular Docker Desktop still works with iptables-legacy?

For /var/run/docker.sock, probably the best solution is to support custom Docker daemon endpoints via config file. We can address that separately in #24.

[gregnr]

Shouldn't be any reason to restrict forwarding for just TCP right?

[th3fallen]

any updates on this?

[mhumeSF]

I wanted to add my experience using colima. Since v0.6.0 colima uses ubuntu as the base vm os – docker-mac-net-connect works as is with the addition of running sudo iptables -A FORWARD -s 10.33.33.1 -j ACCEPT when ssh'd into the vm.

[RafalSkolasinski]

Guys, this would be great as it would allow to provide out of the box support to folks that don't want to use Docker Desktop.

Does this require any further testing?

[tylerauerbeck]

@gregnr Is this something that you see landing in this project? Anything that still needs tested, etc. as part of this (or future) PRs?

[OksiBlack]

@gregnr Are there any news on merge?

[gregnr]

Hey everyone, good news! Colima is now officially supported as of v0.1.7. Also no need to manually symlink your /var/run/docker.sock - the server will now properly check your docker contexts and use your active context (which colima sets when it starts). All iptables rules are accounted for, even with the latest "Direct Access Filtering" rules added in Docker 28.0+. For more info please see #80.

You can upgrade to the latest by running:

brew upgrade chipmk/tap/docker-mac-net-connect
sudo brew services restart chipmk/tap/docker-mac-net-connect

If you encounter any issues, please let me know!