Like many WordPress developers lately my day starts and ends with Varying Vagrant Vagrants. VVV’s really worth a look if you’re still working with MAMP, WAMP, XXAMP, or something similar. Truth.
Sidenote: vvv-site-wizard
Alison Barrett‘s vvv-site-wizard tool is the hotness. And despite what was preached at our local WP meetup… It does work on Windows.
Problem 1: guest additions do not match!
VVV relies on VirtualBox and Vagrant. I encountered some trouble w/ a sub-part of the puzzle this afternoon and I figured I’d share my adventure. Over the last couple days, I’d been noticing this fly by in the console during my morning vagrant up…
Me: “Crap. Maybe I should think about updating that… I guess.”
Thankfully, there’s a plugin for that – vagrant-vbguest!
Solution 1: update guestadditions w/ vagrant-vbguest plugin
Whee! Success!
But-
Problem 2: now folders don’t mount
My VirtualBox GuestAdditions were successfully updated to 4.3.10. Unfortunately, there’s a known bug in that version that prevents mounting shared folders (Note: this will be fixed in 4.3.11). Subtraction. It’s what I literally uttered as an expletive this afternoon. Had I run across the vagrant-vbguest Issue before installing, I would have waited.
At this point, now my vvv environment wouldn’t fully load w/ a vagrant up.
Solution 2: a new symlink!
Thankfully, the fix for this subtraction was found in that GitHub issue I linked above. Felix Rabeprovided (and cited) a solution that worked perfectly for me.
vagrant sshIn my case, it was opening a PuTTY session to the vagrant box.
sudo ln -s /opt/VBoxGuestAdditions-4.3.10/lib/VBoxGuestAdditions /usr/lib/VBoxGuestAdditions
logoutThen, outside the VM:
vagrant reloadFor me, it reloaded successfully, but my dev sites weren’t functioning (MySQL failures) until I ran:
vagrant provisionI was back up and running!
TL;DR
Discovered a problem that wasn’t really affecting me. Decided to fix it; caused major breakage – halting my work day.