Skip to content
Templates for creating vagrant boxes
PowerShell Ruby HTML Batchfile Shell
Branch: rob-current
Clone or download
Pull request Compare This branch is 10 commits ahead of mwrock:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
answer_files
cookbooks/packer-templates
hyper-v-output
scripts
.gitignore
LICENSE
README-HOWTO.md
build.bat
build.ps1
build.sh
hyperv-2012r2.json
hyperv-2016.json
hyperv-nano.json
psakeBuild.ps1
qemu-2012r2.json
readme.md
vagrantfile-windows-nano.template
vagrantfile-windows.template
vbox-2012r2-wmf5.json
vbox-2012r2.json
vbox-2016.json
vbox-nano.json
vbox-win7.json

readme.md

packer-templates

A Packer template that simplifies the creation of minimally-sized, fully patched Windows Vagrant boxes.

This repo and much of its content are covered in detail from this blog post. Also see this post specifically for the Nano Server template.

Rob Allen changes

  1. Merged PR #120
  2. Add README-HOWTO.md
  3. Do not delete unused Windows features as we may want to install them

Prerequisites

You need the following to run the template:

  1. Packer installed with a minimum version of 0.12.3.
  2. VirtualBox - Tested with 5.1.12
  3. Berkshelf - Used to find and vendor Chef cookbook dependencies. This is easist installing via the ChefDK

Vendoring the cookbooks

The Windows 2016 templates use the packer-templates Chef cookbook to provision the image. The cookbook located in cookbooks/packer-templates has dependencies on a few community cookbooks. These cookbooks need to be downloaded. To do this:

  1. cd to cookbooks/packer-templates
  2. Run berks vendor ../../vendor/cookbooks

This downloads all dependencies and saves them in vendor/cookbooks. From here packer will upload them to the image being built.

Invoking the template

Invoke packer to run a template like this:

packer build -force -only virtualbox-iso .\vbox-2016.json

Hyper-V templates

The Hyper-V templates now use the official Hyper-V builder available in the latest versions of packer. I no longer convert Virtual Box images to Hyper-V.

Converting to Hyper-V

As stated above, I no longer convert VirtualBox images to Hyper-V. However that can be useful if you are limited to mac or linux hardware for creating images. This repo includes PowerShell scripts that can create a Hyper-V Vagrant box from the output VirtualBox .vmdk file. This repo leverages psake and Chocolatey to ensure that all prerequisites are installed and then runs the above packer command followed by the scripts needed to produce a Vagrant .box file that can create a Hyper-V file.

See this blog post for more detail on converting VirtualBox disks to Hyper-V.

Troubleshooting Boxstarter package run

Boxstarter is used by some templates for initial provisioning. Due to the fact that provisioning takes place in the builder and not a provisioner, it can be difficult to gain visibility into why things go wrong from the same console where packer is run.

Boxstarter will log all package activity output to $env:LocalAppData\Boxstarter\boxstarter.log on the guest.

You can’t perform that action at this time.