Wireguard tunnel, built in in Docker Desktop to bridge Docker Linux VM to MacOS native network #848
Description
Tell us about your request
I would like Docker Desktop for MacOS to consider deploying a wireguard tunnel to bridge the VM network to the OS native network using iTunes routing table.
There is a tool described in this blog post:
https://medium.com/@tylerauerbeck/making-your-docker-network-reachable-in-osx-e68f998f8249
The code is built in Go, but I believe the concept should be integrated directly in Docker Desktop or as a plugin.
A clear and concise description of what you want to happen or the change you would like to see
Direct access from MacOS native network to docker network for docker host network configuration without using port-forward.
Which service(s) is this request for?
Let us know which product(s) you want this for?
Docker Desktop for MacOS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
The Linux VM layer to run Docker Desktop on MacOS cause major frictions for connectivity and is counter intuitive to how Docker Desktop operate on other platform. This cause significant frustration that decrease the value proposal of Docker Desktop on MacOS.
Community feedback is to migrate to remote development platform. Which is basically a response to: Don't use Docker Desktop it doesn't work.
My scenario problem:
Note: This is just an example. Not to debate if this approach is efficient in a workflow.
Using Docker Desktop on MacOS comes with connectivity problem that drift from other platform user experience, forcing to use port forward and other workaround to bypass the limitation that Docker run inside a Linux VM on MacOS.
When using Kubernete in Docker, it becomes impossible to expose K8S service to the native OS directly without jumping through loop using port-forwarder to the ingress controller.
For example port-forward only works for TCP traffic, and it is impossible to create a port forward to CoreDNS to expose it as contained development DNS service because DNS uses UDP. Same I cannot deploy any UDP based service in Docker.
Using port-forward is also counter intuitive compare to normal host network configuration on other platform.
Are you currently working around the issue?
A clear and concise description of any alternative solutions or features you've considered or are using today.
I haven't found a workaround to UDP service.
Additional context
Add any other context or screenshots about the feature request here.