CLI hanging forever in WSL

[phmarch]

For some reason, the devcontainer cli only works when called from the context of a windows path. When called from home ~, it hangs forever. This was however working just fine before yesterday, no idea what triggered it..

devcontainer 0.40.0
WSL2 / Windows 10 (KB5025367)

I've tried rebooting, wsl --shutdown, updating vscode, wiping ms-vscode-remote.remote-containers folder and reinstalling, resetting the path, I'm out of ideas.

[chrmarti]

It only hangs when you are in your home folder? I guess there is something in that folder that makes it hang? Does it hang when you are in a subfolder of your home folder?

[phmarch]

I hangs in every folder that does not start with /mnt/c. I've tried calling it from a fresh folder too in the root (/test) and it hangs too. which always point to the same path, so I'm really puzzled.. I am starting to think the recent windows update is the culprit, is there a way to run devcontainer in debug mode to see what line is causing the "hanging"?

[rauljmz]

I have exactly the same issue. It only runs from /mnt/c/ and hangs from anywhere else inside the WSL2 file system.

[adburch]

I am hitting the same issue as well. I saw in a previous issue from 2022 (microsoft/vscode-remote-release#5957) that there was a way to install the devcontainer client in WSL2 specifically, but I haven't been able to see how to do that.

[chrmarti]

Could you check if you also see this with the Dev Containers extension 0.288.2 (the previous stable version)?

[adburch]

I didn't see an option for 0.288.2, just 0.288.1. However, it did mostly get rid of the issue. It still seems to hang after finishing whatever I asked it to do ... e.g., "devcontainer --version" prints out 0.35.0, but then it just sits until I do ^C.
devcontainer open . is still not working for me on this version either.