-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NFS / FsEvents failed to run #282
Comments
Do you get the same error if you create a machine directly using |
Doesn't seem to change anything :( |
Can I check if |
I'm wondering why I'm not seeing dinghy/cli/dinghy/http_proxy.rb Lines 92 to 94 in 1a4270e
|
Darn yeah, this is what I've seen a couple times before. I wish I knew what was causing it, or even whether it was docker-machine vs the xhyve driver. That resolver file isn't installed on the VM, it is installed on the MacOS host in |
Can't you think about anything you want me to test to find out where that problem is ? |
I'm not in a great position to figure this one out, I'm afraid. It might be useful to test with Virtualbox, see if you get the same problem with Then I'd file an issue with either the docker-machine-driver-xhyve project or the docker-machine project, or look for an existing issue. |
Doing a macOS reboot handled the NFS issues (port 19091 was still used by a dead process, invisible using lsof, shown using netstat) I was still having issues with DNS, which I solved by using 192.16.8.1.1 instead of 192.168.64.1 as resolver.
|
I've just found out what the real DNS problem was. After running these commands, no more DNS issues inside dinghy :
|
The text was updated successfully, but these errors were encountered: