-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reopen stuck at "Installing Server" #6019
Comments
I can confirm I am having exactly the same issue. It started occuring today. Yesterday I was still able to connect without any issues. I have not made any changes or updades to vscode or extensions. |
@niklasvm Is this when connecting to an SSH server? Are you using some tool for forwarding the SSH connection like @soumroy88 does? @soumroy88 Do you have a way to test this without the port forwarder? |
I am not 100% sure of your first question. I am connecting from Windows via WSL to an EC2 instance running Ubuntu. The container is running on that instance. |
@niklasvm Does 'via WSL' mean you have 'Execute in WSL' enabled in the settings? Could you turn that off and retry? |
That setting is already disabled |
I have reinstalled vscode from scratch and am still unable to connect. I am now receiving the same errors as reported in #6023 |
Update: I have rolled back to vscode 1.62.3 and am getting the originaL error again. This is my full container log:
|
Another update: The process completed after 26 minutes which seems to be a very long for the last command above to run. |
#6023 should be fixed with Remote-Containers 0.209.4. Can you give that a try? (Connecting with SSH has changed a lot between 0.205.2 and now, but I'm not sure it will affect this issue.) |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
I can report this behaviour too |
@meandmymind Could you open a new issue including the Remote-Containers version you are seeing this with and the container log? ( |
@chrmarti unfortunately no because it somehow resolved. maybe other containers version got out, maybe restarting container helped |
Thanks @chrmarti really great work. Pending from long time.
I have below set-up,
When I reopen the container for some reason the Reopen stuck at "Installing Server" state.
Last log
[22496 ms] Start: Run in container: (dd iflag=fullblock bs=8192 count=6543 2>/dev/null; dd iflag=fullblock bs=3238 count=1 2>/dev/null) | tar --no-same-owner -xz -C /vscode/vscode-server-insiders/bin/linux-x64/7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e-insider_1638943187267
At this stage, all my ssh connection to the remote instance, e.g. via putty etc is almost dead. (extremely slow and unresponsive).
But, if I do
Remote : Close remote connection
then all ssh connections are normal again. This is strange!PS: I am using a company internal tool for port forwarding and ssh is done at [email protected]:1337
Update: installation goes through after around 15-20 mins. and now everything is normal again! 👍
Originally posted by @soumroy88 in #2994 (comment)
The text was updated successfully, but these errors were encountered: