Today, when running Vagrant on my Mac, I was greeted with a message “Vagrant will damage your computer”, which blocked it from running.Continue reading post "#4011"
I have moved to using VirtualBox VM’s for my local web development. I use Vagrant and Ansible to set them up. For my site, I use synced folders to share the site files from the local machine to the dev VM. This limits what permissions can be set on the files though, and doesn’t work well for Symfony’s
var folder stuff, eg cache and logs. The normal Symfony permissions for those folders use ACL’s, but those cannot be set on Vagrant synced files. My solution was to create a
/var/www/var folder to store such folders for any sites on the VM, and symlink them into place in the shared folder location. I did this with Ansible so that it would be reproducible. Since I ran into some issues getting it working, I thought I’d blog about it.
Apparently, an update to VirtualBox after version 6.1.26 limited the IP’s usable for network adapters on Mac / Linux hosts. They must now be in the
126.96.36.199/21 range, which is pretty limited and much less easy to remember or type than the
10.*.*.* that I had been using. I had to change my projects to all be in this range and spread out the IPs to avoid collisions between the various projects when I updated VirtualBox a while back.
I recently tried to install vagrant on a Mac OS X.11 (El Capitan) machine, but ran into trouble.Continue reading post "Vagrant on Mac El Capitan problem"
Recently, the ‘vagrant’ user somehow disappeared on a vagrant VM of mine. It may have happened during a
do-dist-upgrade. It took me a while to figure out why
vagrant provision and
vagrant ssh were failing.