Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Sidebar 1" sidebar. Defaulting to "sidebar-1". Manually set the id to "sidebar-1" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /usr/share/wordpress/wp-includes/functions.php on line 4139 Tech Notes » Blog Archive » Vagrant on MacOSX-10.10 and Later

Vagrant on MacOSX-10.10 and Later

vagrant, virtualization Add comments

If your vagrant installation isn’t working in MacOSX-10.10 (“Yosemite”) or 10.11 (“El Capitan”), add the following to your ${HOME}/.profile or ${HOME}/.bashrc

export PATH=${PATH}:/opt/vagrant/bin

By “isn’t working”, I mean “when I type ‘vagrant’, the binary isn’t found”. …and how do we resolve a case of the shell not finding a binary? We “car” the payload of the installer to find out where the binary is! 🙂

The path addition worked for me.

FWIW, this was based on searching to fix my own problem once I had enough to assume I wasn’t the first to run into it. I was looking for a proper fix from the provider, but I found another solution online: Soft link, shared in laracasts:

sudo ln -s /opt/vagrant/bin/vagrant /usr/local/bin/vagrant

For me, this sort of fix is something I’ll forget later in the next install, or an update will nuke and I won’t have a reason why. Sure, my preferred solution is a per-user solution, but it’s a bit more obvious.

Use the one which works best!

Leave a Reply

WP Theme & Icons by N.Design Studio
Entries RSS Comments RSS Log in