Why is the default Vagrant shared folder empty?

Question

The /vagrant directory is empty. It should contain the workspace where my Vagrantfile is located. I can cd /vagrant, but it's empty.

Vagrantfile

VAGRANTFILE_API_VERSION = '2'
VAGRANT_BOX_NAME = 'nomades.local'

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  config.vm.box = 'bento/centos-6.7'
  config.vm.box_check_update = false
  config.vm.hostname = VAGRANT_BOX_NAME

  config.vm.define VAGRANT_BOX_NAME do |dev|
    dev.vm.provider 'virtualbox' do |v|
      v.name = VAGRANT_BOX_NAME
      v.memory = 512
      v.cpus = 2
      v.gui = true
      v.customize ['modifyvm', :id, '--ioapic', 'on', '--vram', '16']
    end

    # Réseau (penser à configurer son /etc/hosts pointant vers cette ip)
    dev.vm.network 'private_network', ip: '192.168.12.2'

    # In order to use VPN
    # dev.vm.network 'public_network', ip: '172.32.0.101'

    # Provision
    dev.vm.provision "ansible" do |ansible|
      ansible.groups = {
          'vagrant' => [VAGRANT_BOX_NAME],
          'servers' => [VAGRANT_BOX_NAME],
      }
      ansible.playbook = 'provision/provision.yml'
      ansible.sudo = true
    end
  end
end

Does this answer your question? [/vagrant not populated with files](https://stackoverflow.com/questions/36270066/vagrant-not-populated-with-files) — ggorlen, Mar 28 '20 at 00:37

score 11 · Accepted Answer · edited Jul 28 '16 at 17:11

11

This happens when vagrant can't modify /etc/fstab and tries to mount the current working directory from the host. Make sure it has permissions to mount the directory.

Run this on the Vagrant guest VM, then logout.

$ sudo /etc/init.d/vboxadd setup

Run this on the host.

$ sudo vagrant reload
$ vagrant ssh

edited Jul 28 '16 at 17:11

Anthony Mastrean

21,850
21
110
188

answered Jul 27 '16 at 16:25

acsrujan

1,011
11
18

Indeed It was a sudo issue, your solution work, thanks! – sab Jul 29 '16 at 14:18
Thanks ! In Windows you don't need to run as administrator the `vagrant reload` – forzagreen Jan 30 '17 at 15:04
1

For me on MacOS, just the `vagrant reload` on the host is enough to get the folders to sync again. – Ivan Carosati Jun 16 '20 at 20:11

score 2 · Answer 2 · answered Mar 27 '20 at 10:10

2

This issue happened to me after manually rebooting the VM (i.e. sudo reboot).

Restarting the machine from the host solved the problem for me:

$ vagrant halt
$ vagrant up

answered Mar 27 '20 at 10:10

michael-slx

665
9
15

This actually helped whereas restarting my host machine didn't :/ – Druckles Sep 20 '21 at 08:18

score 0 · Answer 3 · answered Jul 29 '16 at 10:09

0

you need to define below line in the vagrantfile, . means current directory

config.vm.synced_folder ".", "/vagrant"

answered Jul 29 '16 at 10:09

rikki

51
9

AFAIK there is no extra definition necessary for the /vagrant directory, because it is automatically mapped to current directory. The config says, you need to do (only?) if you need "additional" shares. – Markus Zeller May 29 '19 at 09:20

Why is the default Vagrant shared folder empty?

3 Answers3

Linked