Skip to content
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

Attaching a container to VSCode will cause it to hang and unable to connect #10705

Open
laogonggong847 opened this issue Feb 14, 2025 · 0 comments
Assignees
Labels
containers Issue in vscode-remote containers

Comments

@laogonggong847
Copy link

laogonggong847 commented Feb 14, 2025

Hello @connor4312 hello @roblourens
, When I use 'container attached to Vscode' in Vscode, it freezes and I cannot connect

I saw this link (#9185) and it seems that the issue was resolved through version 0.361.0, but I am already using version 0.394.0. And the difference from them is that I couldn't connect successfully the first time.

I hope to get your help. Below is my log, which has been running for about half an hour without any other output. This is a complete log. Thank you very much.

My specific usage scenario is as follows: I first connect to a remote server in VSCode, and then attach VSCode to the Docker container on the remote server

[3550 ms] Dev Containers 0.394.0 over Remote - Tunnels 1.5.2 in VS Code 1.97.0 (33fc5a94a3f99ebe7087e8fe79fbe1d37a251016).
[3549 ms] Start: 正在解析远程
[3552 ms] Setting up container: /cairunze-cuizhisheng_open_r1
[3552 ms] Host authority: tunnel+zhijiang66
[3556 ms] Start: Loading environment from ExecServer
[3707 ms] Host OS: linux 5.4.0-202-generic
[3707 ms] Host CWD: undefined
[3708 ms] Start: Run: /bin/sh 
[4007 ms] Start: Run in host: echo ~
[4227 ms] /root
[4228 ms] 
[4228 ms] Start: Run in host: id -un
[4384 ms] root
[4385 ms] 
[4385 ms] Start: Run in host:  (command -v getent >/dev/null 2>&1 && getent passwd 'root' || grep -E '^root|^[^:]*:[^:]*:root:' /etc/passwd || true)
[4605 ms] userEnvProbe: loginInteractiveShell (default)
[4605 ms] userEnvProbe: not found in cache
[4606 ms] userEnvProbe shell: /bin/bash
[5199 ms] userEnvProbe PATHs:
Probe:     '/sbin:/usr/sbin:/usr/local/sbin:/usr/lpp/mmfs/bin/:/sbin:/usr/sbin:/usr/local/sbin:/usr/lpp/mmfs/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/usr/local/openmpi/bin'
Container: None
[5678 ms] Start: Run: docker inspect --type container /cairunze-cuizhisheng_open_r1
[6570 ms] Start: Check Docker is running
[6571 ms] Start: Run: docker version
[6916 ms] Client:
[6917 ms]  Version:           24.0.5
 API version:       1.43
 Go version:        go1.20.3
 Git commit:        24.0.5-0ubuntu1~20.04.1
 Built:             Mon Aug 21 19:50:14 2023
 OS/Arch:           linux/amd64
 Context:           default

Server:
 Engine:
  Version:          24.0.5
  API version:      1.43 (minimum version 1.12)
  Go version:
[6982 ms]        go1.20.3
  Git commit:       24.0.5-0ubuntu1~20.04.1
  Built:            Mon Aug 21 19:50:14 2023
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.2
  GitCommit:        
 nvidia:
[6982 ms]   Version:          1.1.7-0ubuntu1~20.04.2
  GitCommit:
[6983 ms]         53b24618a542025b108239fe602e66e912b7d6e2
 docker-init:
  Version:          0.19.0
  GitCommit:        
[6985 ms] Running Dev Containers CLI:   set-up --container-id eebbf29cedca280897d5513c4aa50f0b747815170a72c1e32881d4869311aaa3 --container-session-data-folder /tmp/devcontainers-f7be8515-d61b-4989-b0af-1b577758550d1739517990174 --log-level debug --log-format json --default-user-env-probe loginInteractiveShell --skip-post-create --include-configuration --include-merged-configuration
[6986 ms] Start: Checking for Dev Containers CLI
[7281 ms] Start: Run: /root/.vscode/cli/servers/Stable-33fc5a94a3f99ebe7087e8fe79fbe1d37a251016/server/node /root/.vscode-remote-containers/dist/dev-containers-cli-0.394.0/dist/spec-node/devContainersSpecCLI.js set-up --container-id eebbf29cedca280897d5513c4aa50f0b747815170a72c1e32881d4869311aaa3 --container-session-data-folder /tmp/devcontainers-f7be8515-d61b-4989-b0af-1b577758550d1739517990174 --log-level debug --log-format json --default-user-env-probe loginInteractiveShell --skip-post-create --include-configuration --include-merged-configuration
[7813 ms] @devcontainers/cli 0.72.0. Node.js v20.18.1. linux 5.4.0-202-generic x64.
[7813 ms] Start: Run: docker buildx version
[8062 ms] github.com/docker/buildx v0.19.3 48d6a3927a14668da1a0c4439a6d454a3abbdf05
[8062 ms] 
[8063 ms] Start: Run: docker -v
[8089 ms] Start: Run: docker inspect --type container eebbf29cedca280897d5513c4aa50f0b747815170a72c1e32881d4869311aaa3
[8125 ms] Start: Inspecting container
[8125 ms] Start: Run: docker inspect --type container eebbf29cedca280897d5513c4aa50f0b747815170a72c1e32881d4869311aaa3
[8158 ms] Start: Run in container: /bin/sh
[8162 ms] Start: Run in container: uname -m

@vs-code-engineering vs-code-engineering bot added the containers Issue in vscode-remote containers label Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
containers Issue in vscode-remote containers
Projects
None yet
Development

No branches or pull requests

2 participants