Cannot access my OSX files on containers about boot2docker-vagrant-box HOT 6 CLOSED

Hm... I've just reproduced it. Actually, NFS share is mounted in the VM, but it is not available in the containers.

@sean-brandt, @EloB Have you faced with this issue in your cases? Do you use some workaround?

from boot2docker-vagrant-box.

@sean-brandt, @EloB any ideas?

from boot2docker-vagrant-box.

I found a way to do this

config.vm.synced_folder ".",pwd`.chomp, type: "nfs"``

The boot2docker vm needs to have the same folder structure of the host.

Using the pwd trick worked for me.

from boot2docker-vagrant-box.

@bezelga Thanks!
Wondering, how did it work before... :-|

from boot2docker-vagrant-box.

The boot2docker vm needs to have the same folder structure of the host.

@bezelga, this doesn't really fix this issue though, does it? pwd might map to /home/user/path/to/some/very/specific/directory which: a) is not at all portable; and b) could clobber/hide something inside the VM.

Wondering, how did it work before... :-|

@legal90, so am I. It seems to have stopped working somewhere in 1.7.0 or 1.7.1 (it was working fine in 1.6.0). Was there anything that changed with respect to NFS support since 1.6.0?

from boot2docker-vagrant-box.

@legal90, so am I. It seems to have stopped working somewhere in 1.7.0 or 1.7.1 (it was working fine in 1.6.0). Was there anything that changed with respect to NFS support since 1.6.0?

UPDATE: I now realize that the NFS problems I observed are a different issue than the problem originally described here. I have opened a new issue (#14).

from boot2docker-vagrant-box.