-
Notifications
You must be signed in to change notification settings - Fork 188
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
Specifying custom SSH port does not work #411
Comments
In order to overcome the above, I had to do the following, which less than ideal 😅 :
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Probably relates to test-kitchen/test-kitchen#1159
I have the following scenario at play:
22
disabled but still have the SSH daemon listening on another arbitrary port, say444
kitchen create
the VM just fine. Thekitchen-vagrant
driver will use port forwarding22 => 2222
as per default behaviour.kitchen converge
the VM just fine over port22 => 2222
. This is where Ansible (or any other provisioner) would configure the SSH daemon inside the VM to not listen on port22
anymore but listen on port444
as mentioned above.22 => 2222
default port-forwarding would no longer work. The SSH daemon inside the VM is listening on port444
after its first provisioning.How can I tell
kitchen-vagrant
to connect to the VM via port444
?So far I have tried using the following, either in combination or in isolation, but none of them have worked:
I would expect that if I modify the port settings of the driver, instead of seeing the following:
I would see the following:
But that doesn't happen. It's probably also worth mentioning that the automatically generated "test-kitchen state" (I think it's called..) remains the same all the time:
But I would expect to see
port: 444
. That doesn't happen either.What am I missing?
Thanks!
The text was updated successfully, but these errors were encountered: