-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Vagrant error when mount synced folder #6769
Comments
I get the same error, here is my environment. |
Hi there, I have been unable to reproduce this issue, but it looks like there are a few articles on the internet for workarounds:
Do any of those help? |
@lisi4ok, @sevengo8378 How did you solve the problem? |
We didin`t :) |
@sethvargo Same error here with vagrant-1.8.1-1.fc23.noarch. Version vagrant-1.7.4-2.fc23.noarch was working fine. |
I'm getting the same issue. Setting "nfs: true" didn't work either. Edit: I should have read the following:
To repeat: Guest Additions are needed for shared folders |
At the very least, I think https://www.vagrantup.com/docs/synced-folders/virtualbox.html should be updated to note that it's not going to work out of the box. |
Hi @alfiedotwtf The Vagrant documentation for building boxes requires the base box install the virtualbox guest additions, so it should work just fine out of the box. Perhaps you are using a third-party box that did not properly install the guest additions? What version of Virtualbox are you using? |
I'm on 1.6.5, from Debian Jessie non-free. The box I'm using is Hashicorp's debian/jessie64. Should I be using a different guest? btw: thanks for helping out! |
Hi @alfiedotwtf The latest version of Vagrant is 1.8.1 and is available from https://www.vagrantup.com/downloads.html. We do not recommend using the os packages because they are typically very out and contain and outdated version of Vagrant. Can you please try upgrading to Vagrant 1.8 and see if the issue persists? |
Thanks @sethvargo. Will try it out on the weekend and get back to you. |
Getting same here with debian/jessie64
|
[FIXED] @sethvargo pulling from upstream didn't fix the issue. It looks like the issue was actually the guest and not the host. I was using "debian/jessie64" which didn't work with shared folders as the image did not include vboxsf. Switching to "debian/contrib-jessie64" fixed the issue (it seems obvious now):
|
This issue happen because vagrant box does not have VirtualBox Guest Additions installed. Just follow documentation here https://www.vagrantup.com/docs/virtualbox/boxes.html works for me. I'm using vagrant box
The documentation uses |
from hashicorp/vagrant#6769 Install virtualbox guest additons and ignore error, because X.Org isn't installed.
from hashicorp/vagrant#6769 Install virtualbox guest additons and ignore error, because X.Org isn't installed.
You can also install the vagrant plugin install vagrant-vbguest
vagrant destroy && vagrant up And that works for me. |
@luvejo Thank you!! |
I had the same problem when updated virtual machine to 5.1.20 and installed new VBoxGuestAdditions_5.1.20 I fix it: I think it would be fixed in new releases https://www.virtualbox.org/ticket/16670 |
For me two things fix the problem - One of them is @luvejo's comment above, and the other one is to use NFS: Instead of The first solution is cleaner though, it doesn't cause any warnings later on, but the second one is faster because in the first you'd have to back up your database, and other files you might have that are not shared on your computer. |
Thanks. But the command like |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Hi when i write vagrant up i got this error:
Here it is my Vagrantfile:
Here it is the screen:
https://i.imgur.com/Zt5zrGt.png
P.s. the machine is running but my provision scripts are not applied.
The text was updated successfully, but these errors were encountered: