chef provisioner within 2016 server template fails about packer-templates HOT 3 CLOSED

Hi - ran into this as well and solved by modifying vbox-2016.json to replace the chef-solo section with:

{   
      "type": "chef-solo",
      "remote_cookbook_paths": [
        "c:/windows/temp/packer-chef-solo/cookbooks-0",
        "c:/windows/temp/packer-chef-solo/cookbooks-1"
      ],

In the above note that the remote_cookbook_paths were originally packer-chef-client which does not exist on the guest.

I now have a successful build:

[...cut...]
    virtualbox-iso (vagrant): Compressing: packer-virtualbox-iso-1483422361-disk1.vmdk
Build 'virtualbox-iso' finished.

==> Builds finished. The artifacts of successful builds are:
--> virtualbox-iso: VM files in directory: output-virtualbox-iso
--> virtualbox-iso: 'virtualbox' provider box: windows2016min-virtualbox.box

CloudraticSolutionsLLCs-MacBook-Pro:packer-templates l.abruce$ ls -la $(find . -name windows2016min-virtualbox.box)
-rw-r--r--  1 l.abruce  staff  5133972393 Jan  3 01:47 ./windows2016min-virtualbox.box

I'll try adding the box to vagrant and initializing a vagrant project with it tomorrow. While the size is still 5GB, I am deeply appreciative to Matt for setting this up. I'd been looking for an easier way to spin up Windoze boxes using Vagrant. Rock on!

from packer-templates.

Oh interesting. This may have changed in packer 0.12.1. if you want to submit a pr to fix that's cool but no need at all. I'll fix later. Thanks for posting!

from packer-templates.

Just fixed this. Thanks again!

from packer-templates.