microsoft / microsoft/vscode-remote-release

Attaching Visual Studio Code to Remote Containers Hangs at "Setting up Remote-Containers (show log)"

Open
#6,670 30 comments 7 reactions 1 assignee View on GitHub

@chrmarti is already working on this.

Since May 3, 2022.

bug containers
Dominant language
Dockerfile
Stars
4.2k
Forks
470
Avg merge
1d 1h
Merged PRs (30d)
1

Description

Issue
Trying to attach visual studio code to a container hangs at "Setting up Remote-Containers (show log)". I can attach a shell to the container as well as attach visual studio code to the same container from another computer. To remedy, I reinstalled (clean) VS Code but that did not help either. The Dev Container log shows this:
[26127 ms] Remote-Containers 0.233.0 in VS Code 1.66.2 (dfd34e8260c270da74b5c2d86d61aee4b6d56977).
[26127 ms] Start: Run: ssh xxx-xxxxxxx /bin/sh
[26141 ms] Start: Run in host: id -un

Version of VS Code
Version 1.66.2

What type of remote connection you were using: SSH, Containers, WSL
SSH and Containers

Your operating system
On a Windows 11 Pro Machine, SSH-ed into Ubuntu (18.04.5 LTS)

The remote operating system you are connecting to
A docker container building from python and/or ubuntu

List of extensions that you have installed
image

Reproducible steps (1... 2... 3...) that cause the issue
Right click on running container, click attach Visual Studio Code

What you expected to see, versus what you actually saw
VS Code to open in remote container

Errors from the Dev Tools Console (open from the menu: Help > Toggle Developer Tools)
image

If you are using VS Code Remote - Container support, include your container configuration files if you are able to.
This happens with every container, all of which were functioning properly until recently - hence I do not think providing the container config files will be beneficial as the issue is not specific to certain containers

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.