Hi,
I am trying to provision my ami using a set of custom shell scripts. Sadly
every time they fail I have to recreate an ec2 instance from scratch. This
makes sense when I am deploying in production but at the time of debugging
and trying out different commands it becomes really slow.
Is
Usually I add a null builder to the template. Then you can either A) add a
inline "sleep 3600" start a build with "packer build -only amazon-ebs
template.json". And when it pauses the provisioning in another terminal run
"packer build -only null -var debug_ip=IP -var private_key...
template.json"
Shoot, my current status is "unable to reproduce" when I tried `packer
build` a second time just now. If I see the issue again I'll re-post. If
this is an issue for anyone else I left a link to this page on the GitHub
issue, feel free to chime in.
On Sunday, February 11, 2018 at 1:18:37 PM
Full error message:
==> virtualbox-iso: Failed to send shutdown command: unknown error Post
http://127.0.0.1:3497/wsman: EOF
I opened an issue here: https://github.com/hashicorp/packer/issues/5857
I was redirected to this group.
As for WinRM being "configured incorrectly" it's not; here's my
