- Kickstart plugin not working how to#
- Kickstart plugin not working install#
- Kickstart plugin not working windows 10#
- Kickstart plugin not working code#
- Kickstart plugin not working windows#
You can now run C:\dev\go\src\\mitchellh\packer\bin\packer.exe build and this builder will be available! Things to know Now the built packer.exe is at C:\dev\go\src\\mitchellh\packer\bin\packer.exe.Build it with go build -o bin/packer.exe.
Kickstart plugin not working code#
Kickstart plugin not working install#
Kickstart plugin not working windows#
If few are testing the tooling and most building the tooling are not familiar with Windows environment nuances, its not a scenario optimized for success. One thing I have noticed in "contemporary devops tooling" is that the chances of the tooling working on Windows is sketchy and as for Hyper-V? Good luck! No one uses it in the communities where I mingle (oh yeah.except me it sometimes seems). So I finally took this PR for a spin last week and I was pretty amazed when it just worked. (Oh and hey: Use my discount code SPKR-MWROCK for 15% off General Admission tickets to Hashiconf!) It sure would be nice not to have to bring my VirtualBox rig and just use a Hyper-V builder on my personal laptop. Well next month I will be speaking at Hashiconf about creating windows vagrant boxes with packer. My VirtualBox setup worked fine and I needed to produce both VirtualBox and Hyper-V providers anyways so I was not highly motivated to try out this new builder. So early this year I started hearing mumblings of a new PR to packer for an updated Hyper-V builder. My day to day dev environment uses Hyper-V and ideally this is where I would develop and test Packer builds as well. However, its sometimes a pain to have to switch over to a different environment. Its great to take the exact same image that provisions a VirtualBox VM to also provision a Hyper-V VM. I blogged about this procedure here and I think its still a good option for creating multiple providers on a single platform. I also quickly discovered that I could simply convert the VirtualBox images to VHD format and create a Vagrant Hyper-V provider box without Hyper-V. Converting VirtualBox to Hyper-VĪfter ditching the hope of building Hyper-V images with packer, I resurrected my daughter's half busted laptop to become my VirtualBox Packer builder. Hard to say but as a Packer newcomer and wanting to just get an image built I quickly moved away from using a Hyper-V builder. Likely this is because some things in Hyper-V, like its virtual machine file format had completely changed.
Kickstart plugin not working windows 10#
I started playing with packer in July of 2015 and when I tried this builder on Windows 10 (a technical preview at the time) it just did not work. The Hyper-V builder came in on a version of GO that Packer did not yet support but by the time it did, packer and Hyper-V had moved on. I personally see this like two technology asteroids rocketing past each other. In early 2015 it was announced that MSOpenTech had built a usable Hyper-V builder plugin and there were hopes to pull that into Packer core. The packer ecosystem does provide a plugin model for supporting third party builders. There is no built in Hyper-V builder - the native hypervisor on Windows. Packer currently comes bundled with builders for the major cloud providers, some local hypervisors like VirtualBox, VMware, Parallels, and QEMU as wells as OpenStack and Docker.
Kickstart plugin not working how to#
This post will discuss how to use Taliesin Sisson's PR #2576 to build Hyper-V images with Hyper-V. I'll be blogging about the Chef stuff later. This includes replacing the Boxstarter based install with a Chef cookbook, and also using a native Hyper-V builder. Over the last week I've been playing with some new significant changes to my packer build process.
0 kommentar(er)
