6 ms·

I'm also in the beta, and I like it a lot. It's functionally equivalent to `dlite`, which Nathan LaFreniere has done an extremely good job on. He deserves massi

by STRML 10y ago

I'm also in the beta, and I like it a lot. It's functionally equivalent to `dlite`, which Nathan LaFreniere has done an extremely good job on. He deserves massive credit for making OSX Docker dev bearable and for providing the inspiration for "Docker for Mac". A few issues I've seen: 1. I cannot believe they are using `docker.local`. This hostname will cause nothing but trouble for years to come. DON'T USE `.local`! Apple has decided that `.local` belongs to Bonjour, and due to a longstanding bug with their IPv6 integration, you can expect to see a 5-10s random delay in your applications as Bonjour searches your local network to try to resolve `docker.local`. Yeah, you put it in your `/etc/hosts`? Doesn't matter. Still screws up. Use `docker.dev` or `local.docker`. [http://superuser.com/questions/370559/10-second-delay-for-local-tld-in-mac-os-x-lion http://superuser.com/questions/370559/10-second-delay-for-lo...] 2. -beta8 is screwed up. It won't bind to its local ip anymore. The only option is to port forward from localhost. Unfortunately, Docker isn't offering a download of beta7. Thankfully, I still had the DMG around. 3. The polish is still lacking. Most menu bar items ask you to open up something else. 4. Why "Docker for Mac"? Couldn't the team think of a less confusing name? Now I have "Docker" running "docker". Otherwise - great projects, and again, much credit to @nlf for `dlite`. If you're not part of the beta, check out dlite (https://github.com/nlf/dlite https://github.com/nlf/dlite). It's at least as good as Docker for Mac.

themartorana 10y ago
Have you (or someone) filed a ticket? It's beta, after all. But yeah, good catch.
cpuguy83 10y ago
I do not work on this project, but perhaps this was the move to have the "VPN compatibility mode" enabled by default. Have you tried going to the settings menu and disabling?
akshatpradhan 10y ago
I thought we should be using .local because it was specified in RFC 6762. https://en.wikipedia.org/wiki/.local https://en.wikipedia.org/wiki/.local
- jkrems 10y ago
  The very first paragraph of that article says: > The implementation of both approaches on the same network can be problematic, however, so resolving such names via “unicast” DNS servers has fallen into disfavor as computers, printers and other devices supporting zero-configuration networking (zeroconf) have become increasingly common. Which seems to confirm what the original poster wrote - it sounds like a bad idea using it on OSX where it collides with bonjour.
  - josteink 10y ago
    Or it was a bad idea for apple and bonjour to collide with an established RFC. Why should everyone else change their ways because apple made an error?
    - noinsight 10y ago
      It's not "Apple's error", .local is now an IANA reserved special-use domain name for multicast DNS, i.e. in the same category as .example and .test. http://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml http://www.iana.org/assignments/special-use-domain-names/spe...
    - detaro 10y ago
      That RFC was created because of mDNS/Bonjour, to stop others from using that name for other purposes.
- zurn 10y ago
  That is the multicast dns rfc, and says .local is used for zeroconf and not manual site-local configuration: Any DNS query for a name ending with ".local." MUST be sent to the mDNS IPv4 link-local multicast address 224.0.0.251 (or its IPv6 equivalent FF02::FB)
atonse 10y ago
I just installed docker for mac after getting an invite in this thread, and this is the _only_ issue I'm facing. If I access the IP, it works extremely well. But if I use `docker.local`, then it takes about 5-6 seconds to connect, most of that in name resolution.
lobster_johnson 10y ago
Don't use .dev either, it is/is going to be a TLD now: https://icannwiki.com/.dev https://icannwiki.com/.dev. There are some reserved suffixes, including .localhost and .test: https://iyware.com/dont-use-dev-for-development/ https://iyware.com/dont-use-dev-for-development/.
- secure 10y ago
  .localhost will be dropped as DHCP search domain by systemd-networkd, see https://github.com/systemd/systemd/issues/2258 https://github.com/systemd/systemd/issues/2258 Not sure if that is important for the use-case at hand, but it was the reason why I stopped using .localhost in my LAN (in favor of just using plain hostnames, e.g. “x1”).
- FireBeyond 10y ago
  I typically use .lan - short and to the point.
deleted 10y ago
[deleted]
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 ago
  I 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 ago
  A 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!
matt4077 10y ago
I believe there's a .dev TLD coming, so don't use docker.dev, either. Maybe it's time for an RFC that creates a guaranteed-not-to-be-public TLD, kinda like test.com? Until then, docker.<completely-NSFW-slur> might be your best bet, actually.

by STRML 10y ago

themartorana 10y ago

Have you (or someone) filed a ticket? It's beta, after all. But yeah, good catch.

cpuguy83 10y ago

I do not work on this project, but perhaps this was the move to have the "VPN compatibility mode" enabled by default. Have you tried going to the settings menu and disabling?

akshatpradhan 10y ago

I thought we should be using .local because it was specified in RFC 6762. https://en.wikipedia.org/wiki/.local https://en.wikipedia.org/wiki/.local

jkrems 10y ago
The very first paragraph of that article says: > The implementation of both approaches on the same network can be problematic, however, so resolving such names via “unicast” DNS servers has fallen into disfavor as computers, printers and other devices supporting zero-configuration networking (zeroconf) have become increasingly common. Which seems to confirm what the original poster wrote - it sounds like a bad idea using it on OSX where it collides with bonjour.
- josteink 10y ago
  Or it was a bad idea for apple and bonjour to collide with an established RFC. Why should everyone else change their ways because apple made an error?
  - noinsight 10y ago
    It's not "Apple's error", .local is now an IANA reserved special-use domain name for multicast DNS, i.e. in the same category as .example and .test. http://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml http://www.iana.org/assignments/special-use-domain-names/spe...
  - detaro 10y ago
    That RFC was created because of mDNS/Bonjour, to stop others from using that name for other purposes.
zurn 10y ago
That is the multicast dns rfc, and says .local is used for zeroconf and not manual site-local configuration: Any DNS query for a name ending with ".local." MUST be sent to the mDNS IPv4 link-local multicast address 224.0.0.251 (or its IPv6 equivalent FF02::FB)

atonse 10y ago

I just installed docker for mac after getting an invite in this thread, and this is the _only_ issue I'm facing. If I access the IP, it works extremely well. But if I use `docker.local`, then it takes about 5-6 seconds to connect, most of that in name resolution.

lobster_johnson 10y ago

Don't use .dev either, it is/is going to be a TLD now: https://icannwiki.com/.dev https://icannwiki.com/.dev. There are some reserved suffixes, including .localhost and .test: https://iyware.com/dont-use-dev-for-development/ https://iyware.com/dont-use-dev-for-development/.

secure 10y ago
.localhost will be dropped as DHCP search domain by systemd-networkd, see https://github.com/systemd/systemd/issues/2258 https://github.com/systemd/systemd/issues/2258 Not sure if that is important for the use-case at hand, but it was the reason why I stopped using .localhost in my LAN (in favor of just using plain hostnames, e.g. “x1”).
FireBeyond 10y ago
I typically use .lan - short and to the point.

deleted 10y ago

[deleted]

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 ago
I 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 ago
A 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!

matt4077 10y ago

I believe there's a .dev TLD coming, so don't use docker.dev, either. Maybe it's time for an RFC that creates a guaranteed-not-to-be-public TLD, kinda like test.com? Until then, docker.<completely-NSFW-slur> might be your best bet, actually.