Problems invoking puppet-masterless after using scripts/puppet.bat #46
Comments
I still have not been successful with using In absence of a good solution, I applied the following dirty, dirty hack:
Hopefully this hack is helpful for others who get stuck. I'm looking forward to the day that I can just drop the extra |
Interesting - you've done some good digging on this. Have you tried running packer with the Regarding the shell return code issue, it does sound related to #45. Regarding cygwin, from http://sshwindows.sourceforge.net:
|
Thanks Joe for the background on OpenSSH for Windows and reminding me about the packer Sadly, the |
I've steered away from the puppet-masterless provisioner because of mitchellh/packer#1007. Using a combo puppet-masterless and shell-provisioner is awkward indeed! |
I've run into this issue as well and have completely abandoned trying to get packer to run the puppet provisioner on Windows. Vagrant does a much better job of handling it. I think some if it may have to do with the frustrating issues with ssh and cygwin so that might possibly be a resolution but otherwise to workaround this I would recommend running puppet from a shell provisioner |
This works for me. Maybe there's something here for you as well. in template.json, simplified
and in puppet.ps1
|
Closing, please reopen if more information is needed. |
I see how this workaround can be applied but i fail to see how an awkward workaround can close this issue. The functionality is not there and even if you can do the same via a workaround the bug still exists. I mean there is a provisioner that is not working for windows. |
Seems like packer has an open tracking bug hashicorp/packer#2566. |
…ports Add firewall rules to enable Docker Swarm Mode traffic
What I'm trying to do is repurpose the
windows_2008_r2.json
file by swapping outscripts/chef.bat
forscripts/puppet.bat
and then calling out topuppet-masterless
to install and run my manifests.The
scripts/puppet.bat
file is being executed and puppet is being installed correctly. However, oncepuppet apply
is invoked bypuppet-masterless
theexecute_command
is shown, but my manifest is not being executed and no additional output/errors are shown (even with PACKER_LOG=1 set).For testing purposes, I have been using the following custom
execute_command
:NOTES:
logdest
file does not get createdexecute_command
at the guest Windows VM's command prompt, the execution works.rubyinstaller
in "verysilent" mode. Has anyone seen any limitations with puppet-masterless when using an installer on windows that requires a desktop?ERRORLEVEL
, packer keeps on going. Any suggestions on how to fail-fast? (EDIT: this bullet looks suspiciously like fix passing exit status from shell provision to packer #45)cygwin
is being used under the covers by puppet-masterless. Any other gotchas I should keep in mind when working with customexecute_commands
?I realize that some of these questions may be best asked on the packer forum, but since these questions are very windows specific, I'm wondering if other trailblazers here have already encountered and resolved these issues.
The text was updated successfully, but these errors were encountered: