Hence Wireguard so that I can have an IP address for the container that is visible on the Mac.VMware PowerCLI contains modules of cmdlets based on Microsoft PowerShell for automating vSphere. I can't just map localhost:3306 to the container and put db. in /etc/hosts pointing to 127.0.0.1 because I've already got something on 127.0.0.1 that is using 3306. The client wants to connect to port 3306. With the -p argument you can arrange to have a localhost port mapped to some port on the container.īut in my case that doesn't quite cut it. They don't have IP addresses that are visible to the Mac.
#VMWARE M1 MACBOOK MAC#
On Mac Docker runs a Linux VM and then the containers run in that. I'd just have to put the container IP on the db. /etc/hosts entry. That would also work great if I were running Linux instead of Mac OS, because Docker containers on Linux get IP addresses that are visible. The VM gets an IP address on my Mac, and I use that in the /etc/hosts entry. So I want to make an /etc/hosts entry for db. giving the IP address of the VM or container that I'm running the test server in. I want to run a test version of that server on a VM or in a container, and have that client connect to it, but I do not want to modify the client. I don't want to run the client in a VM or container.
#VMWARE M1 MACBOOK CODE#
The typical case is that I'm testing with client code on my desktop that expects to talk to some particular server, such as db., on some particular port, say 3306. Aliases on the Mac to bring up, take down, and show the tunnel on the Linux VM:Īlias linux-wg-up='docker container run -it -rm -privileged -pid=host -v ~/wg/linux-vm:/wg alpine-wg nsenter -t 1 -u -n -i wg-quick up /wg/nf'Īlias linux-wg-down='docker container run -it -rm -privileged -pid=host -v ~/wg/linux-vm:/wg alpine-wg nsenter -t 1 -u -n -i wg-quick down /wg/nf'Īlias linux-wg-show='docker container run -it -rm -privileged -pid=host -v ~/wg/linux-vm:/wg alpine-wg nsenter -t 1 -u -n -i wg show'.Sudo wg-quick down /Users/tzs/wg/mac/wg.conf Sudo wg-quick up /Users/tzs/wg/mac/wg.conf Here is the Wireguard conf file for the Linux VM (stored on Mac as ~/wg/linux-vm/nf):.Here is my Wireguard conf file for the Mac (stored on Mac as ~/wg/mac/wg.conf).I've generated key pairs for the Mac and the Linux VM.The Docker Mac Linux VM has Wireguard kernel support built in, so you just need an image with the tools in order to configure it. I've made a Docker alpine image, which I named alpine-wg, that is just the base alpine image with the Wireguard tools installed.The Mac IP address on my home network is 192.168.0.2.On the Wireguard tunnel, I've given my Mac IP 10.11.0.2 and the Docker Linux VM IP 10.11.0.3.IP address 10.11.12.128-254 are dynamically allocated to containers that are run with "-network Mynet" but not assigned a static IP. I've got a Docker network name "Mynet" that I put containers on with statically assigned IP addresses (e.g., "-network Mynet -ip 10.11.12.10").In case anyone else finds this useful, here are details of my setup. So I'm using Wireguard to tunnel between the Linux VM and the Mac, so that the container IPs end up visible on the Mac. The container's IP is not visible to the Mac, just to the Linux VM. Bridged networking there just bridges the containers to the Linux VM. ĭocker Mac runs a Linux VM and then runs your containers on that Linux VM. To access something on I'd then just use. I'd simply use bridged networking in the container which would give the container an IP that works for things running on the Linux host. If I were running Docker on Linux this would not be a problem.
If Docker Mac works as well on Apple Silicon I might be able to just stick with that and not need either VMWare or Parallels. Specifically, Wireguard between the Linux VM that Docker Mac creates to run containers and the Mac. That turned out to be not too difficult to deal with by using Wireguard. E.g., if I've got a server that would be foo.com when live on a real server that I'm testing locally in a container, I want it to appear at some_ip:443 on my Mac, not on something like localhost:8443 that Docker maps to port 443 in the container.
The only real snag was that I want services running in a Docker container to be reachable from Mac processes on the same port they would be on when deployed on a real server somewhere. I recently have switched to using Docker for that. Most of my use of VMWare Fusion on my Intel Mac is to run Linux VMs. That's assuming that I decide that I actually need such a product. I don't like that Parallels requires a subscription to get more than 8 GB of RAM in a virtual machine so I'll be sticking with VMWare Fusion when I get an Apple Silicon Mac.
0 kommentar(er)
