NOTE: Most of the contents of this repository have been migrated to the new devcontainers GitHub org (https://github.com/devcontainers). See https://github.com/devcontainers/template-starter and https://github.com/devcontainers/feature-starter for information on creating your own!
I have this issue on two separate machines now, So I'm opening this bug report.
After the update of the extension to v0.275.1 I'm no longer able to open work spaces/folders in containers.
The error I was able to trace is in the "Extension host" output:
2023-02-07 08:43:34.796 [error] Error: Illegal argument: base
at v (c:\Users\Fabje\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:7:1267)
at new ei (c:\Users\Fabje\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:44917)
at Wne (c:\Users\Fabje\.vscode\extensions\ms-vscode-remote.remote-containers-0.275.1\dist\extension\extension.js:337:23068)
at hE (c:\Users\Fabje\.vscode\extensions\ms-vscode-remote.remote-containers-0.275.1\dist\extension\extension.js:337:20963)
at async f (c:\Users\Fabje\.vscode\extensions\ms-vscode-remote.remote-containers-0.275.1\dist\extension\extension.js:337:9132)
at async s.h (c:\Users\Fabje\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:96:108008) remote-containers.reopenInContainer {"value":"ms-vscode-remote.remote-containers","c":"ms-vscode-remote.remote-containers"}
My code is located in my WSL filesystem for performance reasons.
Accessing it from the \wsl$\Ubuntu\home\ or \wsl.localhost\Ubuntu\home path makes no difference.
Pre-release version v0.277.0 has the same behavior
Rolling back to previous versions I was able to trace that the fault is introduced in v0.271.0
v0.270.0 - OK
v0.271.0 - Fails
If I open a container workspace from the "Recent" items list, the container is opened and working.
Workaround
Reverting back to v0.270.0 or previous release v0.266.1 'solves' the issue
FaBjE
commented
1 year ago
I have this issue on two separate machines now, So I'm opening this bug report. After the update of the extension to v0.275.1 I'm no longer able to open work spaces/folders in containers.
The error I was able to trace is in the "Extension host" output:
My code is located in my WSL filesystem for performance reasons. Accessing it from the \wsl$\Ubuntu\home\ or \wsl.localhost\Ubuntu\home path makes no difference.
The issue is the same as https://github.com/microsoft/vscode-dev-containers/issues/1711 but unfortunately reinstalling everything from WSL, Ubuntu, Docker-Desktop, VSCode and the extension does not solve my issue.
Pre-release version v0.277.0 has the same behavior Rolling back to previous versions I was able to trace that the fault is introduced in v0.271.0 v0.270.0 - OK v0.271.0 - Fails
If I open a container workspace from the "Recent" items list, the container is opened and working.
Workaround Reverting back to v0.270.0 or previous release v0.266.1 'solves' the issue
System Info
Steps to Reproduce: