-
Notifications
You must be signed in to change notification settings - Fork 134
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
Timeout while waiting for WinRM with packer 0.12.1 #19
Comments
@ProloG-Shaman, you didnt ask for @obilodeau help yesterday? Did you try to check the open ports on your machine and see which port packer is trying to communicate with. hashicorp/packer#2399 seems to indicate it could be a problem but that it also should be fixed. Vagrant's output generally include forwarded ports, can you paste the full output here. Also, I had problems with the official repos version of Vagrant that were corrected by downloading the package straight from their site. |
@Svieg, I looked at the packer issue you linked, and adding the port for WinRM in the builder_virtualbox_windows.json file seems to have fixed the issue.
|
That's okay if your host is Linux but might be a problem if your on a windows host and winrm is enabled so the ports will collide if I'm not mistaken. I suggest adding this line with the port |
The VirtualBox NAT rule should be automatically created for you. The bug has been fixed and locked upstream so it shouldn't require weird workarounds from our end. Here are my NAT mappings in one of my VMs:
Can you remove your work-around and run the same command as above when your VM is in My feeling is that you already have something on port 2200 on your host or something like that. packer should pick an available port but maybe for WinRM they don't. We'll see once we have the info. |
I removed the work-around and ran the command:
The host port changes each time I run a build. |
While trying to reproduce, I found that this is an upstream regression in packer 0.12.1: hashicorp/packer#4310 I think this is fixed with this PR (which has not been released yet): hashicorp/packer#4321 Avoid packer 0.12.1 for the time being. I ran a successful |
This should be fixed in packer 0.12.2, released a few days ago, according to the changelog. Can you try to reproduce? |
I updated to packer 0.12.2 and I can confirm the issue is fixed for me. |
Excellent. Thanks! |
Hello,
When building a windows 10 64 bit machine with malboxes, I get a timeout while waiting for WinRM. When looking at the machine, it seems to install and boot normally, but no tools are installed and WinRM never becomes available. The command I am running is:
I am running Ubuntu 16.04 LTS 64-bit with Packer version 0.12.1, VirtualBox version 5.0.30 r112061 and Vagrant version 1.8.1. The error output is the following:
The text was updated successfully, but these errors were encountered: