Cannot Reconnect to Active Codespace - Failed to start vs code remote server #136499
Replies: 2 comments 1 reply
-
Exporting the Codespace Logs after the first re-connection failure, I noted that the failure seems to orginate from the fact that the upon trying to reconnnect to the Codespace and devcontainer, the following command initiated by the Codepspace seems to be failing to copy over some cached information:
After checking |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Connecting to Codespace
Question
Body
I am struggling to re-connect with an active Codespace built by this one devcontainer.json.
The devcontainer in question is leveraging
"image": "mcr.microsoft.com/devcontainers/python:1-3.10-bullseye"
and has the remoteUser set toroot
as advised in similar posts (https://github.com/orgs/community/discussions/38410). The devcontainer in question does leverage poetry to install python dependencies.Current process:
Browser error:
VSCode error:
Additional Logs:
Settings Sync
Window
:Leveraging GitHub Cli, I can confirm that the Codespace is still active and even ssh into the Codespace using the following command:
gh codespace ssh -c <codespace-name>
Once sshed into the Codespace, I can confirm that the Codespace is still functioning as normally and that the devcontainer + environment is still the same as I left it.
Attempted Solutions:
Has anybody encountered this error before where they are unable to re-connect to a previously working and active codespace despite no changes to the devcontainer configuration?
I greatly appreciate any knowledge and help offered my way.
Beta Was this translation helpful? Give feedback.
All reactions