-
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
Unaccessible file mounts with VirtualBox #243
Comments
Right now Dinghy only supports NFS mounting one directory at a time, if you use Also I suspect a problem here:
It looks like you're exporting those env vars after dinghy is already running, which means they aren't taking effect. |
Hi, I'm closing this due to inactivity, please re-open if you'd like to continue digging into it. |
Another case related to access rights (Dinghy 4.5.0)
When I log in with
dinghy ssh
I find/Users/ElmarHinz
mapped toroot:root
and those directories are mountable./Volumes
is mapped to the user501:80
and is not mountable.On my local machine both directories have the same user and group settings.
UPDATE: In another try
/Users/ElmarHinz
changed to501:80
, too, while I was browsing the directory.My startup script:
https://github.com/elmar-hinz/TYPO3.docker-development/blob/master/run.sh
There is no error, but the directories are not mounted. (The script works with docker-for-mac).
Possible solution
My other Vagrant based VirtualBox sets
/Volumes/
toroot:root
basically proving the issue is solvable.I don't know what it does different. Maybe it the trick to write to
/etc/exports
. Maybe thealldirs mapall
parameters are OS X special. I don't find them documented for unfsd.(I did remove those lines and recreated dinghy to check troubles are not caused by them.)
The text was updated successfully, but these errors were encountered: