Skip to content


Subversion checkout URL

You can clone with
Download ZIP
A lite development env for BOSH
Shell Smarty Other
Latest commit 295b76d CI Update box version to 9000.69.0


A local development environment for BOSH using Warden containers in a Vagrant box.

This readme walks through deploying Cloud Foundry with BOSH Lite. BOSH and BOSH Lite can be used to deploy just about anything once you've got the hang of it.

  1. Install BOSH Lite a. Prepare the Environment b. Install and Boot a Virtual Machine c. Customizing the Local VM IP
  2. Deploy Cloud Foundry
  3. Troubleshooting
  4. Upgrading the BOSH Lite VM
  5. Miscellaneous

Install BOSH Lite

Prepare the Environment

  1. Install latest version of bosh_cli

    $ gem install bosh_cli --no-ri --no-rdoc

    Refer to BOSH CLI installation instructions for more information and troubleshooting tips.

  2. Install Vagrant

    Known working version:

    $ vagrant --version
    Vagrant 1.6.3
  3. Clone this repository

    $ cd ~/workspace
    $ git clone

Install and Boot a Virtual Machine

Installation instructions for different Vagrant providers:

  • VirtualBox (below)
  • AWS

Using the VirtualBox Provider

  1. Make sure your machine has at least 8GB RAM, and 100GB free disk space. Smaller configurations may work.

  2. Install VirtualBox

    Known working version:

    $ VBoxManage --version

    Note: If you encounter problems with VirtualBox networking try installing Oracle VM VirtualBox Extension Pack as suggested by Issue 202.

  3. Start Vagrant from the base directory of this repository, which contains the Vagrantfile. The most recent version of the BOSH Lite boxes will be downloaded by default from the Vagrant Cloud when you run vagrant up. If you have already downloaded an older version you will be warned that your version is out of date.

    $ vagrant up --provider=virtualbox
  4. When you are not using your VM we recommmend to Pause the VM from the VirtualBox UI (or use vagrant suspend), so that VM can be later simply resumed after your machine goes to sleep or gets rebooted. Otherwise, your VM will be halted by the OS and you will have to recreate previously deployed software.

  5. Target the BOSH Director. When prompted to log in, use admin/admin.

    # if behind a proxy, exclude both the VM's private IP and by setting no_proxy ( is introduced later)
    $ export,
    $ bosh target lite
    Target set to `Bosh Lite Director'
    $ bosh login
    Your username: admin
    Enter password: *****
    Logged in as `admin'
  6. Add a set of route entries to your local route table to enable direct Warden container access every time your networking gets reset (e.g. reboot or connect to a different network). Your sudo password may be required.

    $ bin/add-route

Customizing the Local VM IP

The local VMs (virtualbox, vmware providers) will be accessible at You can optionally change this IP, uncomment the private_network line in the appropriate provider and change the IP address.

  config.vm.provider :virtualbox do |v, override|
    # To use a different IP address for the bosh-lite director, uncomment this line:
    # :private_network, ip: '', id: :local

Deploy Cloud Foundry

See deploying Cloud Foundry documentation for detailed instructions. Alternatively run ./bin/provision_cf from this repository.


Upgrading the BOSH Lite VM

If you wish to upgrade the BOSH Lite VM, you can run the following commands from the root of the bosh-lite directory. Make sure you have the latest version of this repository checked out. WARNING: these operations are destructive, and essentially amount to starting from scratch.

$ vagrant box update
$ vagrant destroy
$ vagrant up --provider=DESIRED_PROVIDER


Something went wrong with that request. Please try again.