<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>vagrant on bascht.com</title><link>https://bascht.com/tags/vagrant/</link><description>Recent content in vagrant on bascht.com</description><generator>Hugo -- gohugo.io</generator><language>de-de</language><lastBuildDate>Thu, 12 Dec 2013 00:00:00 +0000</lastBuildDate><atom:link href="https://bascht.com/tags/vagrant/index.xml" rel="self" type="application/rss+xml"/><item><title>Choosing a Vagrant default provider</title><link>https://bascht.com/tech/2013/12/12/choosing-a-vagrant-default-provider/</link><pubDate>Thu, 12 Dec 2013 00:00:00 +0000</pubDate><guid>https://bascht.com/tech/2013/12/12/choosing-a-vagrant-default-provider/</guid><description>If you are using the VMWare Fusion or Workstation Providers with Vagrant, you are likely to have VirtualBox Installation left on your machine. At least that&amp;rsquo;s the case for me.
So if you&amp;rsquo;re annoyed about the Vagrant default behaviour
$ va status Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed. Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires this to be available on the PATH.</description></item><item><title>Bootstrap a Vagrant VM before running the provisioner.</title><link>https://bascht.com/tech/2013/06/08/bootstrap-a-vagrant-vm-before-running-the-provisioner./</link><pubDate>Sat, 08 Jun 2013 00:00:00 +0000</pubDate><guid>https://bascht.com/tech/2013/06/08/bootstrap-a-vagrant-vm-before-running-the-provisioner./</guid><description>This might not be the most elegant way to deal with this problem, but often enough I find myself in a situation in which I try to run bootstrapping-stuff in my puppet-manifests or run a simple apt-get update command before provisioning with Puppet.
One way to solve this dilemma is to bootstrap custom Vagrant boxes with a tool like Veewee, which has served me well for more than a few times now.</description></item></channel></rss>