Add support for running within WSL2 #57
Conversation
|
|
|
It would be great to include this feature in next release. I also ran into this limitation in Linux environment in WSL2 where I have all dev tools, forcing me to switch to Powershell in Windows. |
|
This sounds great, would definitely use it! |
camjjack
changed the title
|
Hi @camjjack thanks for opening up this change. Overall it looks good. I will pull it down and give it a round of testing, and a closer review. I'm releasing 1.1.1 today to get out the TPM change but will follow up with this change for the next release. |
|
In the meantime, can you please rebase onto main to pull in the latest changes to the plugin. |
|
Thanks @nywilken, I've rebased onto main and pushed. |
nywilken
changed the title
There was a problem hiding this comment.
@camjjack apologies for the delayed response. I was unable to prioritize this review until now. I do apologize. I tested your changes and I am able to build in a WSL environment without issue (well I had to play with my default switch a little for hyperv) but that is outside of WSL. I'll rebase and merge in your changes.
Support for running from within WSL2.
Similar to vagrant it will work when run from a windows filesystem within wsl i.e.
/mnt/c/Users/user/...Further,
PACKER_CACHE_DIRneeds to be set to a path on the windows filesystem.This is all I needed for my testing to work.
/mnt/c/Users/user/packer-plugin-hyperv$ PACKER_CACHE_DIR=/mnt/c/Users/user/.packer packer build ...Closes #38