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
Improve nfs.server.mount.require_resv_port check #1275
Comments
Looks like project containers are not able to mount the codebase from the host using NFS. At the same time, the default NFS mount looks to be fine in your case:
I wonder if switching the volumes mode at the project level will make a difference in your case:
|
@lmakarov changing the mount type to "bind" worked for me. Thank you! Is there a way to set that globally for all projects? |
Yes - The problem, though, is that we've just switched (in the latest release) to using It's not clear what the issue with your setup is and whether this is a one-off problem or not. This will need to be further tested and investigated. |
FWIW, I'm getting the same or similar problem with a fresh Docksal install and a Platform.sh project.
|
I feel like there is some change in |
It's not Catalina. @shelane 's colleague has the same error with 10.14.6
|
@steveoliver @murathalici the issue was solved for @shelane via See
BUT for Shelane (and likely for you) it does not look like this. The line with require_resv_port is either absent or commented out. Please try and let know if it helps you. |
@achekulaev any idea why this happens? We have the code that handles that configuration in Lines 2615 to 2623 in d9ed003
|
In Shelane's case the line was commented out, the code does not check for this. I guess it can be the same in other cases. |
In my colleague’s case, he had previously installed Vagrant which affected both the nfs.conf file and the exports file. |
@lmakarov I've been banging my head against a wall trying to get personal desktop to run a project for a day or more - your solution to to add the line Anywise! Thank you so much for having a fix so I can continue to work. |
Thanks @lmakarov it's working for me as well
|
Thank you my friend I spend around one week to figure it out, the issues was that after the cli had been created the file system had no permissions to write something in the volume that was not present, I tried your recommendation and it worked so nicely, I am new to docksal, so this was really useful. Thank you again for sharing this. |
Description
Problem/feature description...
Just got a brand new Mac that's running OSX 10.14.5 and I'm unable to get db and cli containers to work using VirtualBox. It works fine if I switch to docker desktop.
Describe the results you received:
fin p start
Output of
fin config
:fin config output
Output of
fin sysinfo
:fin sysinfo output
The text was updated successfully, but these errors were encountered: