-
Notifications
You must be signed in to change notification settings - Fork 1.3k
NFS support #817
Comments
@chiedojohn fwiw and as a 'workaround' you can just try to use my vagrantified boot2docker which does just that ... |
Thanks @AntonioMeireles I will check that out. That could be a game changer. Things are running so slowly as it currently stands! |
You can use nfs inside boot2docker, it is just not documented I have done the following steps in order to have nfs share on boot2docker :
|
Hey @joelwurtz, I am getting the following after attempting to mount the nfs on the client: And I did change 192.168.59.3 to my host IP address as assumed. Any ideas? Thanks! |
Scratch that last statement. It looks like I wasn't supposed to change 192.168.59.3 to my host IP. Looks like it's working. Thanks for your help. |
Thanks again for all of your help. I went ahead and wrote a quick tutorial for whoever else comes across this page on how to automate that process so it's automatically is configured each time boot2docker is started. |
@chiedojohn perhaps you should create a pull request to add this as a document to the docs? |
@thaJeztah good call. The pull request has been submitted. |
What is the likelihood of getting NFS support? Shared folders are extremely slow. With Vagrant, I would just use the following in my vagrant file and things worked like a charm.
config.vm.synced_folder '.', '/vagrant', nfs: true, :mount_options => ['actimeo=2']
Is there anything on the radar for getting the same kind of option for boot2docker?
Thanks,
The text was updated successfully, but these errors were encountered: