Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save dclarke-modus/b1d59318eb23123788dde2ea39936c27 to your computer and use it in GitHub Desktop.
Save dclarke-modus/b1d59318eb23123788dde2ea39936c27 to your computer and use it in GitHub Desktop.
MacBook-Pro:techstack deanclarke$ vagrant up
Bringing machine 'web' up with 'virtualbox' provider...
Bringing machine 'api' up with 'virtualbox' provider...
==> web: Importing base box 'joomlatools/box'...
==> web: Matching MAC address for NAT networking...
==> web: Checking if box 'joomlatools/box' is up to date...
==> web: Setting the name of the VM: techstack_web_1497247379834_70806
==> web: Clearing any previously set network interfaces...
==> web: Preparing network interfaces based on configuration...
web: Adapter 1: nat
web: Adapter 2: hostonly
web: Adapter 3: hostonly
==> web: Forwarding ports...
web: 3306 (guest) => 3307 (host) (adapter 1)
web: 22 (guest) => 2222 (host) (adapter 1)
==> web: Running 'pre-boot' VM customizations...
==> web: Booting VM...
==> web: Waiting for machine to boot. This may take a few minutes...
web: SSH address: 127.0.0.1:2222
web: SSH username: vagrant
web: SSH auth method: private key
web:
web: Vagrant insecure key detected. Vagrant will automatically replace
web: this with a newly generated keypair for better security.
web:
web: Inserting generated public key within guest...
web: Removing insecure key from the guest if it's present...
web: Key inserted! Disconnecting and reconnecting using new SSH key...
==> web: Machine booted and ready!
[web] GuestAdditions versions on your host (5.1.22) and guest (5.0.16) do not match.
Reading package lists...
Building dependency tree...
Reading state information...
linux-headers-4.2.0-27-generic is already the newest version.
The following NEW packages will be installed:
dkms
0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded.
Need to get 65.4 kB of archives.
After this operation, 351 kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main dkms all 2.2.0.3-1.1ubuntu5.14.04.5 [65.4 kB]
dpkg-preconfigure: unable to re-open stdin: No such file or directory
Fetched 65.4 kB in 0s (155 kB/s)
Selecting previously unselected package dkms.
(Reading database ... 81903 files and directories currently installed.)
Preparing to unpack .../dkms_2.2.0.3-1.1ubuntu5.14.04.5_all.deb ...
Unpacking dkms (2.2.0.3-1.1ubuntu5.14.04.5) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Setting up dkms (2.2.0.3-1.1ubuntu5.14.04.5) ...
Copy iso file /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
mount: block device /tmp/VBoxGuestAdditions.iso is write-protected, mounting read-only
Installing Virtualbox Guest Additions 5.1.22 - guest version is 5.0.16
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.1.22 Guest Additions for Linux...........
VirtualBox Guest Additions installer
Removing installed version 5.0.16 of VirtualBox Guest Additions...
Stopping VirtualBox Additions ...fail!
(Cannot unload module vboxguest)
Removing existing VirtualBox DKMS kernel modules ...done.
Removing existing VirtualBox non-DKMS kernel modules ...done.
Stopping VirtualBox Guest Addition service ...done.
Copying additional installer modules ...
Installing additional modules ...
vboxadd.sh: Starting the VirtualBox Guest Additions.
An error occurred during installation of VirtualBox Guest Additions 5.1.22. Some functionality may not work as intended.
In most cases it is OK that the "Window System drivers" installation failed.
vboxadd.sh: Starting the VirtualBox Guest Additions.
vboxadd.sh: failed: modprobe vboxsf failed.
Could not find the X.Org or XFree86 Window System, skipping.
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims: 5.0.16
VBoxService inside the vm claims: 5.1.22
Going on, assuming VBoxService is correct...
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims: 5.0.16
VBoxService inside the vm claims: 5.1.22
Going on, assuming VBoxService is correct...
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims: 5.0.16
VBoxService inside the vm claims: 5.1.22
Going on, assuming VBoxService is correct...
Restarting VM to apply changes...
==> web: Attempting graceful shutdown of VM...
==> web: Booting VM...
==> web: Waiting for machine to boot. This may take a few minutes...
web: SSH address: 127.0.0.1:2222
web: SSH username: vagrant
web: SSH auth method: private key
==> web: Machine booted and ready!
==> web: Checking for guest additions in VM...
web: No guest additions were detected on the base box for this VM! Guest
web: additions are required for forwarded ports, shared folders, host only
web: networking, and more. If SSH fails on this machine, please install
web: the guest additions and repackage the box to continue.
web:
web: This is not an error message; everything may continue to work properly,
web: in which case you may ignore this message.
==> web: [vagrant-hostsupdater] Checking for host entries
==> web: [vagrant-hostsupdater] found entry for: 33.33.33.58 joomlatools
==> web: [vagrant-hostsupdater] Writing the following entries to (/etc/hosts)
==> web: [vagrant-hostsupdater] 192.168.33.11 joomlatools # VAGRANT: ae295a497cd18f5b612d4c8899526433 (web) / 29b4d336-641e-4767-9880-e7d2c639b719
==> web: [vagrant-hostsupdater] This operation requires administrative access. You may skip it by manually adding equivalent entries to the hosts file.
==> web: Setting hostname...
==> web: Configuring and enabling network interfaces...
==> web: Installing NFS client...
==> web: Exporting NFS shared folders...
==> web: Preparing to edit /etc/exports. Administrator privileges will be required...
==> web: Mounting NFS shared folders...
==> web: Mounting shared folders...
web: /vagrant => /Users/deanclarke/vagrant/joomla/techstack
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:
mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant
The error output from the command was:
/sbin/mount.vboxsf: mounting failed with the error: No such device
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment