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
synced_folder fails for NFS on Sonoma 14.4 #13364
Comments
I am working with @dfreudenberger and having the same problem. It looks like replacing "nfsd restart" with "nfsd update" here. Though I am not able to run vagrant from a checkout and install the parallels plugin and therefore not really able to provide a fix right now. |
I too am experiencing the same problem. |
We are affected too:
|
Same here |
I'm also on 14.4 and I'm also having this same issue: ==> default: Installing NFS client... mount -o vers=3 10.211.55.2:/Users/user/Work/test.com/site /vagrant-nfs-test.com Stdout from the command: Stderr from the command: mount.nfs: an incorrect mount option was specified |
Yes, unfortunately bumped into the same issue today... |
Also happens with Sonoma 14.4.1 :( |
Same - manually running sudo nfsd update in terminal resolves |
I don't think anyone else has mentioned it, but I'm having the same issue with VirtualBox - this issue isn't Parallels specific. |
FYI I have the same issue issue using VMWare Fusion |
I came upon this thread while searching for the error message. Unrelated to Vagrant, I have this issue on my Mac. The |
It's working, thanks. |
@unlovedsam What exactly did you do? I've run the command before the vagrant up command - no change. After the vagrant up command exits, no change. In a separate terminal at the point when the kickstart error is emitted, no change. Still unable to mount my synced_folder. |
It seems to be a UDP issue in my case with Ubuntu 22.04. Forcing UDP off in the Vagrantfile seems to sort that out (also probably with the help of |
I’m also having this issue but couldn't fix it by running |
All I can say is that I now have it working but I am not sure why having tried every suggested combination above and these combinations were not previously working. Most recently I did the following:
But honestly I can't say for certain which of these got NFS working between host and guest files. AND, even though I am manually checking that the files are in sync, the launchctl kickstart error message is still being generated FYI I added a file to
Note that changing |
Debug output
https://gist.github.com/dfreudenberger/7e894870dc739cba7876fef4983c8508
Expected behavior
synced_folder should mount the specified path using NFS.
Actual behavior
Apple decided to limit the access to kickstart which is currently used to restart the NFS daemon. Therefore the mount operation fails.
Edit:
It seems like Vagrant doesn't actually use kickstart by itself; instead, it runs "sudo nfsd restart" which causes the error mentioned. Perhaps modifying this line to use
update
instead ofrestart
could solve the problem.sudo nfsd restart Could not kickstart service "com.apple.nfsd": 1: Operation not permitted /bin/launchctl exited with status 1
Reproduction information
Vagrant version
Vagrant 2.4.1
Host operating system
MacOS Sonoma 14.4
Guest operating system
Fedora
Steps to reproduce
Vagrantfile
The text was updated successfully, but these errors were encountered: