Packer: winrm_host is ignored, at least on Amazon EBS

Created on 1 Mar 2018  ·  4Comments  ·  Source: hashicorp/packer

Using packer compiled from source as I debugged. So latest.
Platform: Windows 2008
Debug output doesn't show anything useful without additional logging added for the host value

winrm_host is simply ignored. Doesn't matter what I set it to.

Looking in step_connect_winrm.go in the waitForWinRM function it seems Host is the only variable that is obtained by calling out to s.Host(). The remaining WinRM variables are obtained by directly hitting s.Config.WinRM*

bug communicatowinrm docs

Most helpful comment

I need this value - I'm attempting to provision a Windows instance in a private subnet through an SSH tunnel for port 5985 so I need this value to be 127.0.0.1

Are you saying there's no way to do this since the value seems to be ignored for EC2?

All 4 comments

this looks like a docs bug, thanks for pointing it out. We don't expect users to set winrm_host. It looks like maybe it's only used the vmware builder

I need this value - I'm attempting to provision a Windows instance in a private subnet through an SSH tunnel for port 5985 so I need this value to be 127.0.0.1

Are you saying there's no way to do this since the value seems to be ignored for EC2?

I was trying docker builder with WinRM communicator and also noticed (according to debug log) it seemed to ignore the winrm_host value I’d specified (also set to 127.0.0.1). See issue 3 on #6006

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

Was this page helpful?
0 / 5 - 0 ratings