VM fails at "Mounting NFS shared folders" about ghost-vagrant

[jgable]

[default] The guest additions on this VM do not match the installed version of
VirtualBox! In most cases this is fine, but in rare cases it can
cause things such as shared folders to not work properly. If you see
shared folder errors, please update the guest additions within the
virtual machine and reload your VM.

Maybe it has something to do with that line? We have some info about updating guest additions in the README.

[jgillich]

Hasn't changed much:

[jakob@thinkpad Ghost-Vagrant]$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] Running any VM customizations...
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
GuestAdditions versions on your host (4.2.18) and guest (4.1.12) do not match.
Reading package lists...
Building dependency tree...
Reading state information...
dkms is already the newest version.
linux-headers-3.2.0-54-generic is already the newest version.
The following packages were automatically installed and are no longer required:
  libxfixes3 libxcomposite1 xfonts-encodings x11-xkb-utils xserver-xorg-core
  xserver-common libgl1-mesa-dri xfonts-utils libxfont1 xfonts-base
  libfontenc1 libxdamage1 libxrandr2 libxkbfile1 libllvm3.0
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Downloading VirtualBox Guest Additions ISO from http://download.virtualbox.org/virtualbox/4.2.18/VBoxGuestAdditions_4.2.18.iso
Copy iso file /home/jakob/.vagrant.d/tmp/VBoxGuestAdditions_4.2.18.iso into the box /tmp/VBoxGuestAdditions.iso
mount: warning: /mnt seems to be mounted read-only.
Installing Virtualbox Guest Additions 4.2.18 - guest version is 4.1.12
Verifying archive integrity... All good.
Uncompressing VirtualBox 4.2.18 Guest Additions for Linux............
VirtualBox Guest Additions installer
Copying additional installer modules ...
Installing additional modules ...
Removing existing VirtualBox DKMS kernel modules ...done.
Removing existing VirtualBox non-DKMS kernel modules ...done.
Building the VirtualBox Guest Additions kernel modules ...done.
Doing non-kernel setup of the Guest Additions ...done.
Starting the VirtualBox Guest Additions ...done.
Installing the Window System drivers ...fail!
(Could not find the X.Org or XFree86 Window System.)
An error occurred during installation of VirtualBox Guest Additions 4.2.18. Some functionality may not work as intended.
Cleaning up downloaded VirtualBox Guest Additions ISO...
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /vagrant
[default] -- /tmp/vagrant-puppet/manifests
[default] -- /tmp/vagrant-puppet/modules-0
[default] Exporting NFS shared folders...
Preparing to edit /etc/exports. Administrator privileges will be required...
[sudo] password for jakob: 
Redirecting to /bin/systemctl restart  nfs-server.service
[default] Mounting NFS shared folders...

I guess the Xorg error is because it isn't installed in this image so it can be ignored?

[jgable]

Can you try ssh'ing in, doing the apt-get update && apt-get upgrade dance and then exiting and bouncing the vm via a vagrant halt && vagrant up?

[jgable]

Also, did you update your path in the VagrantFile to match the path to your Ghost repo? You'll need to change the GhostSourcePath

[jgillich]

The GhostSourcePath is correct, of course.

After disabling my firewall (iptables -F), it works:

vagrant@vagrant-ubuntu-precise-64:~$ ls /home/jakob/devel/Ghost/
config.example.js  config.js  content  CONTRIBUTING.md  core  Gruntfile.js  index.js  LICENSE  node_modules  package.json  README.md  SECURITY.md

So this is probably something that could be added to the README.

But shouldn't the path inside the VM be /home/vagrant/code/Ghost instead of the one in GhostSourcePath?

EDIT: Oh damn. I edited the wrong line. The comment above line 39 is a bit misleading:

# NOTE: This should match your path to the Ghost source

[jgable]

Yes, it should be /home/vagrant/code/Ghost.

Don't have a Linux machine to test with. Seems all you Linux people have
problems, which is funny for an operating system that should be mostly used
by people used to configuring weird things to get them to work.

[jgillich]

Well, in this case the issue was that Fedora is pretty secure by default. Might not happen as often elsewhere. :)

Thanks for your help!