-
Notifications
You must be signed in to change notification settings - Fork 23
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
Is the current plugin support Windows VM ? #118
Comments
For the record, the underneath error is vagrant side related to the newest OpenSSL library. The vagrant client is also not stopping the build when it shows the error. I don't know if you could do something |
Last question : the current packer builder is compatible with winssh ? |
Hi @flassagn, Lots to unpack here! Regarding whether or not you can use SSH for communicating with a Windows instance, that depends if the instance has an sshd running or not. Seems like this box does expose one, since the plugin managed to connect with SSH (though it seems there was one issue with agent forwarding, but that didn't prevent it from working). The WinRM error you got I'm not sure to understand where it's coming from, I failed to grep that in the sources of Packer/SDK/Vagrant plugin, so it's hard to say what produces it.
To be clear, the "underneath error" you mention is the WinRM failed to execute error with the Regarding winssh, I'm not sure I know what that is, could you elaborate a bit on that? Is this Microsoft's fork of OpenSSH that they embed with Windows these days? |
Exactly, the error seems related to the newest distribution (I'm using archlinux) which has OpenSSL 3 and WinRM. You could find additionals info at hashicorp/vagrant#13076 (comment). |
I'm currently trying to build a Windows Vagrant box with
packer-plugin-vagrant
without success.Communicators
First, could we used the SSH communicator with windows box ?
Build silent errors
Second, I see errors in log but the build is mark as success, but I don't see any
package.box
generatedMy packer file content
The shell log
If you take a look during
==> vagrant.gusztavvargadr: Calling Vagrant Up (this can take some time)...
, I gotThe text was updated successfully, but these errors were encountered: