Open DannyBen opened 1 year ago
Same problem
@DannyBen Have you solved this problem?
@DannyBen Have you solved this problem?
Yes. I have reverted to Ubuntu 20.... :) The quality of the "Vagrant on Windows for running Linux" solution is degrading consistently. Sooner or later, we will have to face the music.
I have the same issue. Pretty sure the issue is not too hard to fix...
It's happened on almalinix/9 too, hope author can solve the problem please
config.vm.synced_folder "./data", "/data", type: "nfs", mount_options: ['nolock'], nfs_udp: false
@DannyBen This is my solution on Ubuntu22, still work on Almalinux/9
config.vm.synced_folder "./data", "/data", type: "nfs", mount_options: ['nolock'], nfs_udp: false
@DannyBen This is my solution on Ubuntu22, still work on Almalinux/9
If I recall correctly, when not using UDP the performance is unacceptable. I since moved to Arch linux without NFS.
I seem to be stuck in an endless error loop.
My setup used to work without a problem on Ubuntu 20, but now it fails on Ubuntu 22 (Ubuntu vagrant guest on Windows 11 host).
My Vagrantfile config:
With this, it seems like the plugin adds
vers=3,udp
again, so when runningvagrant up
, this error occurs:Note the command was prepended with
ver=3
andudp
again.ver=3 udp
from my options, it fails with another error (mount.nfs: an incorrect mount option was specified
)udp
, it mounts properlyudp
from my options, it still fails.I think that there is some broken logic that adds these options when it shouldn't.