What happened?
Setup DevPod with docker provider and VSCode as the open button,
Everything boots up just fine when pressing the open button to the workspace it starts to load gets to the point of the code command and stalls.

If I take that command and run it in PowerShell nothing happens the cursor just returns to new line, typing in code . for example still works fine and opens vscode in my current directory as expected so it's not a path issue.
What did you expect to happen instead?
I would expect that VSCode opens to the directory of the dev container workspace like it does when you open with vscode browser.
How can we reproduce the bug? (as minimally and precisely as possible)
All I did was install devpod, setup docker provider (localhost), added the golang workspace template and tried to open with vscode.
My devcontainer.json:
Golang quickstart template
Local Environment:
- DevPod Version: 0.3.7
- Operating System: windows 11
- ARCH of the OS: AMD64
DevPod Provider:
- Local/remote provider: docker
- Default provider settings I just pressed docker and save
Anything else we need to know?
Nope.
What happened?
Setup DevPod with docker provider and VSCode as the open button,
Everything boots up just fine when pressing the open button to the workspace it starts to load gets to the point of the code command and stalls.
If I take that command and run it in PowerShell nothing happens the cursor just returns to new line, typing in
code .for example still works fine and opens vscode in my current directory as expected so it's not a path issue.What did you expect to happen instead?
I would expect that VSCode opens to the directory of the dev container workspace like it does when you open with vscode browser.
How can we reproduce the bug? (as minimally and precisely as possible)
All I did was install devpod, setup docker provider (localhost), added the golang workspace template and tried to open with vscode.
My
devcontainer.json:Golang quickstart template
Local Environment:
DevPod Provider:
Anything else we need to know?
Nope.