-
Notifications
You must be signed in to change notification settings - Fork 300
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
WSL2 devcontainer on windows host wslpath -w vs -u #9891
Comments
Make sure you are using the latest versions of VS Code and the Remote-SSH and Dev Containers extensions. If it still doesn't work, please append the Dev Containers log from when this happens. ( |
For what it's worth, I am setting up a relatively new machine, and having this exact issue. I setup Devcontainers on Windows 11 according to the documentation (Docker for Windows with WSL2 backend, 'Execute in WSL' enabled). When I try to load a container, the path that is shown and fails is clearly a Windows-style one, and the command above it uses the -w flag. As soon as I rolled the Extension back to 0.309.0 and reloaded things, the pathing issue was fixed and the container spun up perfectly. I can try to dig in and provide better logs later, I just needed to get this working as quickly as possible, and the extension downgrade did it! |
Here's the relevant piece
Here's the full log
|
Hi @chrmarti do you need any other info here? Thanks! |
@kdarby-cqg Could you share your devcontainer.json and user settings JSON? Are you starting from a local window open on |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Hi @chrmarti I am starting vscode from c:\code\cqg\bts\spark_sdk_sample I attached the devcontainer.json |
"same here, rolled back and it now works..."
Originally posted by @tukutela in #9064 (comment)
This issue seems not to be resolved in later version, a rollback to Dev Containers 0.309.0 is still necessary. Am I missing something?
The text was updated successfully, but these errors were encountered: