You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
devpod provider add kubernetes # v0.1.6 at this time
devpod up github.com/microsoft/vscode-remote-try-node --ide vscode
VSCode is opened but no extensions are installed (i.e. streetsidesoftware.code-spell-checker in this case).
The agent vscode-async command is waiting forever, cat /tmp/vscode-async.pid.streams:
Wait until vscode-server is installed...
ad infinitum
I would expect the code to be going through the ReleaseChannelStable path (I've not asked for anything otherwise...) but the directory structure in the container is ~/.vscode-server/cli/servers which is the expectations of the other releasechannel...?
What did you expect to happen instead?
Extensions installed..
How can we reproduce the bug? (as minimally and precisely as possible)
As above.
Local Environment:
DevPod Version: v0.5.4
Operating System: mac
ARCH of the OS: ARM64 local, AMD64 in K8s.
DevPod Provider:
Cloud Provider: aws EKS
Kubernetes Provider: Client Version: v1.29.1, Server Version: v1.26.14-eks-b9c9ed7
Local/remote provider: ssh
Anything else we need to know?
The text was updated successfully, but these errors were encountered:
What happened?
Happens with my own (simple) devcontainer.json, but also with https://github.com/microsoft/vscode-remote-try-node/blob/main/.devcontainer/devcontainer.json.
devpod provider add kubernetes # v0.1.6 at this time devpod up github.com/microsoft/vscode-remote-try-node --ide vscode
VSCode is opened but no extensions are installed (i.e. streetsidesoftware.code-spell-checker in this case).
The
agent vscode-async
command is waiting forever,cat /tmp/vscode-async.pid.streams
:ad infinitum
I would expect the code to be going through the ReleaseChannelStable path (I've not asked for anything otherwise...) but the directory structure in the container is ~/.vscode-server/cli/servers which is the expectations of the other releasechannel...?
What did you expect to happen instead?
Extensions installed..
How can we reproduce the bug? (as minimally and precisely as possible)
As above.
Local Environment:
DevPod Provider:
Anything else we need to know?
The text was updated successfully, but these errors were encountered: