Thanks for the tips! Just to clarify: you're building the windows machine on the MacOS host? (as it seems that your hosts.ini file points to 127.0.0.1)
I would try use the shell-local command, but my machine is being built on VSphere (setup by Packer), and so I won't have the IP address needed to run the ansible command locally I think... On Thursday, 23 November 2017 22:42:08 UTC, Jordan Borean wrote: > > You won't be able to run the ansible command on the Windows host itself as > Ansible does not run as a controller on Windows. You can still use > shell-local as that runs local to what is running Packer itself and not to > the host being built itself, which in your case would be the MacOS host. In > the end I've been able to create a wide range of Windows images using the > virtualbox-iso provisioner on a Mac OS X and Fedora host using this method. > > An example of how I did this using the default winrm connector as well as > answer to a lot of the questions I had when it came to Packer and Windows > can be at this blog post > http://www.bloggingforlogging.com/2017/11/23/using-packer-to-create-windows-images/ > . > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/77b58e15-891a-4c41-965e-b4ac611c4c1e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
