This has the packer template, and all the other artifacts needed to build a windows 2012 R2 VirtualBox based Vagrant box for windows. If you want to quickly jump into things and forgo the rest of this post or just read it later, just read the bit about instaling packer or go right to their download page and then clone my packer-templates github repo. box file for creating new VirtualBox VMs with this image. Optimize the image with Boxstarter, installing all windows updates, and shrinking as much as possible.Using a Packer template To load the ISO in a VirtualBox VM and customize using a Windows Autounattend.xml file.Downloading free evaluation ISOs (180 day) of Windows.Here is a synopsis of what this post will walk through: This post is a culmination of my previous posts on this topic but on mean a raw foods diet - its 100% automated and repeatable. Type a command, go to sleep and you wake up with new windows images ready for consumption. The process can still be lengthy, but there is no baby sitting.
This post shows a way that ends much of this agony and adds considerable predictability to a successful outcome. Often there are small hiccups that require starting over or backtracking. There is a lot of babysitting done along the way. box file, testing and uploading the images.Įven if all goes smoothly, the entire process can take around 8 hours. There is considerable time involved in each step: downloading the initial ISO from microsoft, installing the windows os, installing updates, cleaning up the image, converting the image to any alternate hypervisor formats (I always make both VirtualBox and Hyper-V images), compacting the image to the vagrant. I cringe whenever I have to refresh my vagrant boxes. These posts explain the multiple steps of preparing the base box and then the process of converting that box to the appropriate format of your preferred hypervisor. I've written a couple posts on how to create vagrant boxes for windows and how to try and get the base image as small as possible.
0 kommentar(er)
