-
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows WSL with Hyper-V fails #420
Comments
@doxinho could you run this with additional logging and include the log files? It would also be helpful if you could include your |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
馃懟 Brief Description
Running test-kitchen in Windows WSL with Hyper-V returns:
Version
1.6.1
Environment
Windows 10 v2004, standard linux cookbook
Scenario
Trying to run test-kitchen within WSL using Hyper-V with vagrant, but it fails to find powershell.exe? I believe the issue is with this line?
kitchen-vagrant/lib/kitchen/driver/helpers.rb
Line 44 in c44be79
Steps to Reproduce
Install Hyper-V:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
Install WSL:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Install chefdk & vagrant in wsl:
curl https://omnitruck.chef.io/install.sh | sudo bash -s -- -P chefdk -c stable
&https://releases.hashicorp.com/vagrant/
Enable vagrant in WSL:
export VAGRANT_WSL_ENABLE_WINDOWS_ACCESS="1"
Allow chef to use the embedded ruby installation instead of anything native:
sudo ln -s /opt/chefdk /opt/chef
&export PATH=/opt/chef/embedded/bin:$PATH'
Configure vagrant to utilize Hyper-V:
export VAGRANT_DEFAULT_PROVIDER=hyperv
Expected Result
test-kitchen runs successfully and spins up a Hyper-V VM
Actual Result
Fails immediately due to not finding powershell.exe
The text was updated successfully, but these errors were encountered: