Closed puchupala closed 1 month ago
Manually installing VS Code Server using the following command prior to connecting make it works. Note that I was using the script from https://github.com/b01/dl-vscode-server/tree/main
curl -L https://raw.githubusercontent.com/b01/dl-vscode-server/main/download-vs-code-server.sh | BUILD=stable bash -s -- "linux"
Random guess: This might be related to the fact that the home dir inside the pod is nfs-mounted shared dir.
Does it work when you change the home folder to a local folder in the container/pod?
Does it work when you change the home folder to a local folder in the container/pod?
Yes, it does. Is this a supported use case? I expect the connection to be slow but it probably should at least connect. 🤔
I would expect it to work with all filesystems having regular filesystem behavior. Could you enable trace logging for Dev Containers in the user settings? That will make the log show progress from the dd
command that is copying the server bits over. It would be interesting to know if that makes progress at all or just hangs.
Somehow, I could no longer reproduce the issue. I removed ~/.vscode-server
, and the installation went fine. However, there is a new issue.
I have 2 pods, both sharing the same home directory via NFS. Attaching to Pod A and installing vscode-server
work fine.
However, when I try to attach to Pod B, I get 2 error dialogs.
Could not fetch remote environment
and
Failed to connect to the remote extension host server (Error: WebSocket close with status code 1006)
Since this is not related to the problem described in this issue, please allow me to close this issue and perhaps start a new one.
The problem with sharing the entire home folder between pods is that Dev Containers remembers the port the server listens on in a file in the home folder. The second pod's log shows ECONNREFUSED 127.0.0.1:39187
because it got the port of the server running on the first pod.
I see... Thank you very much for the clarification. Should I open a new ticket or is this an unsupported use case? (shared home dir)
It is unsupported, you could open an issue to ask for support though. (Or try some workaround like making ~/.vscode-server
a symlink to a folder in the container.)
I'm trying to attach VSCode to my dev pod in a remote K8S cluster but it hang during the following step and eventually error (see logs below).
ubuntu:22.04
-based internal-use containerDoes this issue occur when you try this locally?: No (creating a new dev container locally works fine) Does this issue occur when you try this locally and all extensions are disabled?: No