In a nutshell, Vagrant is a tool for working with virtual environments, and in most circumstances, this means working with virtual machines. Vagrant provides a simple and easy to use command-line client for managing these environments, and an interpreter for the text-based definitions of what each environment looks like, called Vagrantfiles. This post will describes how to install a CHEF environment with Vagrant. introduction. CHEF is an system and infrastructure automation framework. It allows to define how is configured a server or an infrastructure based on recipes which are scripts written with a ruby base DSL(domain specific language) to configure an element and cookbooks Proxy Configuration Plugin for Vagrant. A Vagrant plugin that configures the virtual machine to use specified proxies. This is useful for example in case you are behind a corporate proxy server, or you have a caching proxy (for example polipo).. The plugin can set: At last step of provisioning procedure, vagrant auto-generate powershell script that have to launch chef client at bootstraped machine. When vagrant attempts to run those powershell script - it fails. Now. When it happen - I connect to those new bootstraped machine and try to run those script manually. And it also fails vagrant Cookbook. Installs Vagrant 1.6+ and manages vagrant plugins w/ a custom resource. If you are not familiar with Vagrant, read about it here: Chef must run as a privileged user (e.g., root). (or other), you may need to manually remove and clean up anything leftover, such as running Ignore Vagrant, its a VM provisioner that is used with Puppet or Chef. With that said, go with either one. But also keep your eye on Docker for self contained software deployments - I think folks are generally switching to Puppet/Chef for managing base system configuration, Docker for handling software services and deploys. Setting up Chef and Vagrant on Windows 7 under Cygwin Jul 15 2012. At a previous job we were res