Thanks for this, I hit the same thing with a template which had previously
worked.
I got rid of quickconfig and used the code from the windows example and
template works again.
If you get stuck at this point if you can connect to the temp vm and poke
around you may well find like I did that win
Thanks, Jon.
Just out of curiosity, what version of Windows was your template?
I have tried the code from the website and am still having no luck.
However, I will double-check that WinRM is firing up on the VM before
raising an issue.
Cheers all,
Dave.
On Friday, April 13, 2018 at 4:54:38 P
I also have this issue. Were you able to resolve it?
On Monday, November 30, 2015 at 4:31:35 AM UTC-8, Sandeep Sharma wrote:
>
> Hi
>
>
> I have three aws accounts so trying to use variable file for AMI
> permission.
>
> variables.json
>
> {
> "ami_users" : ["1", "", "333
I have several images in a pipeline being built by Packer, all using the
same template, more or less.
High-level:
- AWS EBS Builder
- Copies resulting AMI to several regions
- Puppet Masterless Provisioner
- Several Shell Provisioners
All of the other images run through without any
The management won't let us run packer builds on vSphere yet. So we're
stuck standing up a VM with nested virt enabled on it.
When I attempt to do a build, I get this in the log:
2018/04/14 01:01:03 packer: 2018/04/14 01:01:03 [DEBUG] Error getting SSH
address: IP lookup failed: None of the fou
