Vagrant: Synced folder on centos/7 not syncing.

[fabionitto]

Versions:

vagrant 1.8.1
VirtualBox: Oracle VM VirtualBox Manager 4.3.34_Ubuntu
Host rsync:  version 3.1.0  protocol version 31 
Box: centos/7

Actual behaviour:

fabionitto@SE-136406:~/centos_test$ vagrant init centos/7
A 'Vagrantfile' has been placed in this directory. You are now
ready to 'vagrant up' your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
'vagrantup.com' for more information on using Vagrant.
fabionitto@SE-136406:~/centos_test$ vim Vagrantfile 
fabionitto@SE-136406:~/centos_test$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'centos/7'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'centos/7' is up to date...
==> default: Setting the name of the VM: centos_test_default_1453998738947_53033
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2200 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2200
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: 
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default: 
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: No guest additions were detected on the base box for this VM! Guest
    default: additions are required for forwarded ports, shared folders, host only
    default: networking, and more. If SSH fails on this machine, please install
    default: the guest additions and repackage the box to continue.
    default: 
    default: This is not an error message; everything may continue to work properly,
    default: in which case you may ignore this message.
==> default: Installing rsync to the VM...
==> default: Rsyncing folder: /home/fabionitto/centos_test/ => /home/vagrant/sync
fabionitto@SE-136406:~/centos_test$ vagrant ssh
[vagrant@localhost ~]$ cd sync/
[vagrant@localhost sync]$ ls
Vagrantfile
[vagrant@localhost sync]$ touch foo
[vagrant@localhost sync]$ ls
foo  Vagrantfile
[vagrant@localhost sync]$ exit
logout
Connection to 127.0.0.1 closed.
fabionitto@SE-136406:~/centos_test$ ls
Vagrantfile

Expected behaviour:

That is not consistent with the expected behaviour of Synced Folders.

[fabionitto]

I found on documentation that

The rsync synced folder does a one-time one-way sync from the machine running to the machine being started by Vagrant.

The rsync and rsync-auto commands can be used to force a resync and to automatically resync when changes occur in the filesystem

By default the rsync__auto option is true, which means the folder should automatically sync, unless it was explicit set to false on the centos/7 Vagrantfile.

This is probably not the place to this problem, so I guess this issue can be closed.

[albarki]

@falconed , this is because there is No guest additions on this base box.
you can try another box, here is one i use,
vagrant box add centos7 https://github.com/holms/vagrant-centos7-box/releases/download/7.1.1503.001/CentOS-7.1.1503-x86_64-netboot.box

[pembo13]

Just to clarify, does this mean that rsync__auto simply does not work with the official centos/7 box? If so, docs really don't make it clear that these features are dependent on the individual boxes.

[mbigras]

@fabionitto What is the syntax for rsync command to force a sync?

[hashibot[bot]]

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.