-
Notifications
You must be signed in to change notification settings - Fork 189
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
SSH Config not sufficient in WSL2 #458
Comments
like what I'm imagining is getting the WIN10IP in an envrionment variable and then just using that as an option in kitchen.yml as ENV['winip'] or something similar? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🗣️ Foreword
Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.
👻 Brief Description
A clear and concise description of what the bug is.
I'm trying to build the default bento boxes from the tutorial on wsl2; which unlike wsl1 is a virtual machine in itself. but as I've been attempting to do this with kitchen create I'm getting the following error:
Which doesn't happen when I'm doing it on the windows side:
Version
[Version of the project installed]
![image](https://user-images.githubusercontent.com/22901019/125612803-9877e9e1-ca6a-44f2-9542-092af50d2cc0.png)
I believe that the version of the
gem kitchen-vagrant
I'm using is 1.9.0Environment
[Details about the environment such as the Operating System, cookbook details, etc...]
My windows build is 19043.1055
and I've kept everything upto date on the chef side of things as well as with wsl2
Scenario
[What you are trying to achieve and you can't?]
I'm trying to run
kitchen create
which hopefully will bring up two the <ubuntu-default 2004> box in wsl2 and it fails at trying to connect to the vm through sshExpected Result
[What are you expecting to happen as the consequence of above reproduction steps?]
It just gets stuck trying to connect to vm through ssh which doesn;t work
The text was updated successfully, but these errors were encountered: