-
Notifications
You must be signed in to change notification settings - Fork 293
WSL Unknown path format #371
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
Comments
I upgraded to WSL2 on the insider preview and get the same issue when running inside of a point not in /c/ (changed mount path). Flipping the !isWsl check in the bellow code (line 103-107) If I'm running inside WSL, but running my python code from inside the linux side of the filesystem and not the /c/ or /mnt/c/ mount the code checks that I have to have one of the following formats: |
Having this same issue as well. |
This became an issue starting in 5.x, 4.3.0 works well. |
any solutions ? Using WSL2 with Docker-Desktop
Your Environment Information ---------------------------
Operating System: linux
Node Version: 14.5.0
Framework Version: 1.74.1
Plugin Version: 3.6.15
SDK Version: 2.3.1
Components Version: 2.31.12 |
I had the same issue.
For me
So it does NOT immediately I am guessing this was added for the original WSL on windows and hasn't been updated for WSL2. |
Any update or fix for this bug? |
I am also looking for an update or fix as this is still occurring... |
How is it not fixed yet ? WSL 2 has been out for a while now... |
Thanks so much @tyjenkins your solution worked for me. |
This was fixed in 5.4.x and can be closed. |
On WSL Ubuntu 18.04LTS I'm getting
when I use
dockerizePip=true
in node_modules/serverless-python-requirements/lib/docker.js,
getBindPath
is being called withservicePath=="/home/davidg/lambda-serverless-test/.serverless/requirements"
That function seems to require the
servicePath
point to somewhere on my windows filesystem (/mnt/c/...) Is there no support for projects located in my wsl home directory?FWIW I followed the README instructions regarding running under WSL and did step 1 and 2.
The text was updated successfully, but these errors were encountered: