Brian Palmer

hmm if it's logging the file touches but not logging any errors, I really don't know how it could be failing in a way that wouldn't also affect an independently-run...

What VM provider are you using? NFS is running in udp mode because we ran into a lot of errors with tcp mode when this was first all set up...

Hm I can't reproduce this on my machine using the xhyve backend, I'll have to set up a Virtualbox env when I get a chance. It looks like IPv6 DNS...

I'm able to repro the problem using the Virtualbox backend. I tried creating another VM directly with `docker-machine create` and couldn't repro there, so that narrowed it down to what...

Heh yes, we have a half dozen or so devs using Linux laptops. I wish I had a good answer, it's still a thorny problem for us. So far we've...

You can already map arbitrary ports on `*.docker` to container ports, using the normal `docker run -p` option, so I'm assuming you're talking about mapping ports on the host's native...

I've been meaning to add this to the FAQ, thanks for the reminder: https://github.com/codekitchen/dinghy/blob/master/FAQ.md#the-docker-client-reports-errors-like-x509-certificate-is-valid-for-192168xy-not-192168xz I haven't seen it happen as often as whenever you switch networks though. It seems to...

Yeah interesting idea, it seems like that'd work.

As stated in the FAQ answer I linked to, the fix is to run `docker-machine regenerate-certs dinghy`

Well, darn. We originally used to select a random port to run NFS on with each start, exactly because of this problem. But I could no longer reproduce the problem...