-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Type ENTER to exit
Windows 2012R2
#76
Comments
Type ENTER to exit
Windows 2012R1Type ENTER to exit
Windows 2012R2
I typed "ENTER" + return and it completed. |
While it does prompt you to press enter, this should not matter because the last thing the boxstarter script does is setup winrm. Normally, that alone should appow packer to connect to the box and sysprep it and complete the process. Since that is not happening, this usually means something is misconfigured in the packer winrm settings. This has been tricky because depending on which version of packer you are using, different settings will break. The settings currently in this repo were set with v 0.12.1. So the first thing I'd try is using that version of packer. |
Hi Matt, So I have no idea what the issue is. I'll try again at some point. It completed and I have a patched basebox (with UK settings) which is sufficient for me for another 179 days! Regards, |
I'm having the same problem but it's happening at the end of the temp_BoxstarterPackage install and I have to hit enter for it to proceed with turning on winrm. At this stage Packer isn't even connected, it's all Boxstarter and Chocolately. |
I may not fully uinderstand your scenario but it is expected for boxstarter to end prompting you to type enter before it closes the console. At the very end of the boxstarter package, it sets up winrm and at that point Packer is supposed to be able to connect and drive the rest of the image build. Are you prompted after all the updates are installed and the entire package completes? Thats the expectation. If thats the case, it means Packer must not be able to make a winrm connection with the vm. |
What I'm currently doing (as you can see in the other bug I opened #233) is running first a package which simply adds the box to the domain, then running an install of MSSQL 2014. It stops at the Enter prompt before the section that starts winrm and also prompts to enter when the winrm section completes. The temp_BoxstarterPackage install finishes successfully (I did several tests to verify it completely finishes) and once it gets handed back to the main script, it stops and requests me to hit enter. It seems to me in the testing I've done that if there is a reboot needed, things finish properly, but as the MSSQL install doesn't require a reboot, it just stops. |
As a followup to this, I've discovered that if I have two lines doing 'Install-BoxstarterPackage' I get the Enter prompt, but if I make the script do this only once, it doesn't give me that prompt until after winrm is turned on. I'm going to try merging the two packages together and see if it will work successfully with that. |
Morning
When I use
packer build -force -only virtualbox-iso .\vbox-2012r2.json
I get the following within the VirtualBox image.
Not sure what to do next, as pressing
ENTER
does not do anything other than closing the prompt.Tried with the
WMF5
version and it gets stuck at the same point.Any ideas?
The text was updated successfully, but these errors were encountered: