-
Notifications
You must be signed in to change notification settings - Fork 32
nfs simple example "failed: Connection refused" #48
Comments
Hello @ehernandez-xk ! You're lucky, I'm just having a bit of time ongoing to solve few Github issues :) 1st try on my way (same Vagrant, latest box, on 10.11.4), stuck during NFS mounting. Strange since the tests passed. I'm going to debug. On your side, you can help by trying to uninstall Fuse and ntfs-3g (=> NTFS <> NFS :) ), and try again, posting here your results. Thanks ! |
Hi @dduportal, I'm very lucky so =0) I already uninstall Fuse and ntfs-3g without errors. (I restarted my Mac)
I'm going to paste it when the console shows the output. |
It looks like there are no timeout, I still waiting |
VAGRANT_LOG=info vagrant up
|
Hey, But in my project shows the error:
the password is not requested. |
I forgot the variable, sorry So it looks like with 1.6.1 works fine.
With the following folder shows the error failed: Connection refused
Temporally I will use this version 1.6.1 |
OK, I found the problem: latest version of boot2docker does not have anymore the nfs-client started. Short term solution for you, create this script and vagrant reload, it works fine then, until vagrant destroy -f:
I'm working on:
|
I like your approach, This can be run in the provision phase? or is to late for that? I will wait to the new release =0) many thanks |
OK, my bad, I needed to sleep when trying to reproduce :) In fact, you don't have anything to configure within your Vagrantflie, regarding NFS. The test done by the harness suite juste do this (from doc. https://github.com/dduportal/boot2docker-vagrant-box#tips--tricks ): $ export B2D_NFS_SYNC=1
$ vagrant up Step for you:
=> Technical explanation:
I'm not very pleased of my work since you should be able to enable this within the Vagrantgfile also. I'm thinking about implementing a Ruby variable as flags to check within your Vagrantfile, or applying some logic that will detect if you have mount points over NFS and add the nolock options. Don't know yet. Can you please confirm that it is working now ? Thanks to having taken time to send me feedback and debug logs ! |
Tks man. take a rest! When the B2D_NFS_SYNC is enabled. the default sync is using "." the current directory, buy in my case I need to go back in the directories. "../" because my docker host Vagrantfile lives in dockerHost directory. so I decided to copy your config
And works fine. Is that ok? |
Thats is perfect ! I propose you to contribute to the documentation ? Thanks for the feedbacks ! |
Sure! I will |
I have posted my question in stackoverflow related to fns and the message failed: Bad file descriptor vagrant-and-docker-nfs-failed-bad-file-descriptor Using Vagrant and Docker as a provider.
So I decided to test a sample example posted by @dduportal #10 (comment)
And after vagrant up, the execution hangs for a while and finally it shows an error
This is the output
The error:
I Previously installed (I don't know if was necessary)
I'm used:
The text was updated successfully, but these errors were encountered: