I\'ve used Vagrant for a while on a windows 7 system. Now I\'ve a new PC with windows 10. I installed Oracle Virtual Box and Vagrant and I try to start a machine with the comman
I have solved this issue as below when use cent/7 at Windows 7.
Check the box synced_folder at C:\Users[username]\.vagrant.d\boxes\centos-VAGRANTSLASH-7\1602.02\virtualbox\Vagrantfile
config.vm.synced_folder ".", "/home/vagrant/sync", type: "rsync"
Override the defition at project Vagrantfile for directory mapping.
config.vm.synced_folder ".", "/home/vagrant/sync", type: "virtualbox"
I imagine the box might be prepared at non Windows system, this case can be happened on many boxes, such as fedora/23-cloud-base.
First of all this is not a bug it is expected behavior on Windows because the rsync is absent on Windows.
If you faced with this problem and want to use the rsync as a mechanism to sync folders you should:
That's all.
Thank you for your attention and have a nice day :-)
Using Vagrant/VirtualBox (5.06) on Windows7 with centos/7 box from Atlas: could not find rsync on the path. So, I installed via cygwin as suggested (had other stuff to install as well, including openssh). No joy. Tried changing the shared folder config to "virtualbox" rather than "rsync". No joy. Oh, forgot to check if the VirtualBox guest additions were in the box: they were not. Rsync worked bettter, but still chocked at the end (could not chdir to the source directory of the shared folder). However, the "type: virtualbox" config did work!
So the datapoint is: centos/7 with guest additions added and shared folder type set to "virtualbox" (overriding the box setting) on windows 7 works.
Worked out of the box (no changes, no guest additions) on MacOS.
I was able to fix this problen using another bos from C:\Users{your_username}.vagrant.d\boxes\box\subfolder\virtualbox\Vagrantfile
And adding
# Load include vagrant file if it exists after the auto-generated
# so it can override any of the settings
include_vagrantfile = File.expand_path("../include/_Vagrantfile", __FILE__)
load include_vagrantfile if File.exist?(include_vagrantfile)
Seems like a bug. You can report it here. But it seems that your bug has been already reported as the issue 6631.
Nevertheless you can try to add rsync
to your PATH
and check the result. You can do it in 2 ways:
vagrant up
from its Cygwin TerminalI found in another forum that the local Vagrant directory is mounted as "/vagrant" via rsync. This is set in the box itself, you can check by opening
C:\Users\{your_username}\.vagrant.d\boxes\debian-VAGRANTSLASH-jessie64\8.2.2\virtualbox\Vagrantfile
and see the setting
config.vm.synced_folder \
".",
"/vagrant",
type: "rsync"
to get around this I added the following line in my local Vagrantfile
config.vm.synced_folder ".", "/vagrant", type: "virtualbox"
and the error was resolved