Happy you got it working for your usecase! It seems to offer more familar ground to those already having experience of working with Docker for Windows as well as added extensibility regarding multiple docker networks.
As a Linux user (without regular access to a Mac) trying to better support co-workers in a local environment with a single docker network, the aims of my shim were very tightly scoped: achieve the minimum amount of difference between the experience on Linux and that on OSX and support at least one docker network to which the host was automatically a member. To that end your solution probably isnāt ideal for me and the extra steps around creating a priviledged container and having to manually configure routes make me shy away from it.
That said I know thereās a definite hunger in the community for multiple network support and Iām glad youāve (if youāll excuse the pun) bridged the gap and indeed that youāre willing to champion this issue as the sooner our hacks are no longer required and this functionality has proper baked in the support the better for everyone!
Guys, I managed to route traffic to containers and from containers using a dns solution for Docker for linux and for mac. I tried tap solution but didnāt worked.
There are some issues, like cannot mantain a opened connection to container for a long time, but you can access services inside the container without publishing any port.
@zanaca Looks interesting, will take a deeper look once I get the chance.
In regards to your issues with the TAP solution, could you clarify what problems you had?
This way we can help others who may stumble upon this thread.
I detailed a workaround for K3s with TunTap and MetalLB but it feels kludgy for sure. Dropping a link here in case it proves valuable for anyone who doesnāt want to run Kubernetes in a *nix VM on Mac.
and indeed that youāre willing to champion this issue as the sooner our hacks are no longer required and this functionality has proper baked in the support the better for everyone!