3 ms·
> I cannot believe they are using `docker.local`. This hostname will cause nothing but trouble for years to come. We are indeed moving away from `docker.local
by avsm 10y ago
> I cannot believe they are using `docker.local`. This hostname will cause nothing but trouble for years to come.
We are indeed moving away from `docker.local` in Docker for Mac. There have actually been two networking modes in there since the early betas: the first one uses the OSX vmnet framework to give your container a bridged DHCP lease ('nat' mode), and the second one dynamically translates Linux container traffic into OSX socket calls ('hostnet' or VPN compatibility mode).
Try to give hostnet mode a try by selecting "VPN compatibility" from the UI. This will bind containers to `localhost` on your Mac instead of `docker.local` and also let you publish your ports to the external network. One of our design goals has been to run Docker for Mac as sandboxed as possible, and so we cannot just modify the /etc/resolv.conf to introduce new system domains such as ".dev".
We've been iterating on the networking modes in the early betas to get this right, so beta9 should hopefully strike a good balance with its defaults. It's also why we've been holding a private beta, so that we can make these kinds of changes without disrupting huge numbers of users' workflows. Your feedback as we figure it out is very much appreciated!
- JoyceBabu 10y agoI had signed up for Docker for Mac beta on the same day of the announcement. I haven't received an invite yet. Did I miss the invite, or isn't the invitation sent on the 'first come first serve' basis?
- djs55 10y agoA minor addition: to use 'localhost' in beta 8 you may need to also run the internal debug command: pinata set native/port-forwarding true In previous betas this setting was implied by "VPN compatibility" mode, but in beta 8 it was made an independent setting. In beta 9 using localhost will be the default -- as avsm says we've been iterating on the network configuration trying to find the most compatible / least surprising defaults. Hopefully after beta 9 it will be stable on "localhost".
- tzaman 10y ago> It's also why we've been holding a private beta, so that we can make these kinds of changes without disrupting huge numbers of users' workflows. Pretty much every developer's workflow is already heavily disrupted by not having access to beta. I've spent days trying to get my filesystem notifications up with dlite and Dinghy (succeeded with the latter). So whatever you guys do, it's still better than what's currently available. Keep up the awesome work!