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

.vscode-remote-containers folder create in Remote-SSH without interaction #10679

Open
chrmarti opened this issue Feb 4, 2025 · 1 comment
Open
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers

Comments

@chrmarti
Copy link
Contributor

chrmarti commented Feb 4, 2025

From #10505: It seems we create that as a side effect of checking if there is a devcontainer.json in the current workspace folder.

@chrmarti chrmarti self-assigned this Feb 4, 2025
@chrmarti chrmarti added bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers labels Feb 4, 2025
@pmoris
Copy link

pmoris commented Feb 5, 2025

Thanks, Christof!

Just to clarify, this happens when there is no devcontainer.json file present, but simply when connecting to a remote without specifying a particular workspace folder.

The extensions I have installed are all those in the remote development pack:

Expand list

code --list-extensions --profile test-profile
ms-vscode-remote.remote-containers
ms-vscode-remote.remote-ssh
ms-vscode-remote.remote-ssh-edit
ms-vscode-remote.remote-wsl
ms-vscode-remote.vscode-remote-extensionpack
ms-vscode.remote-explorer
ms-vscode.remote-server

And lastly, since this was tested on a new profile that inherits some of the base settings from my default one, unsetting the shared remote.SSH.serverInstallPath setting, appears to resolve the issue.

Expand log with serverInstallPath set:

[174 ms] Dev Containers 0.394.0 over Remote - SSH 0.116.1 in VS Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba).
[173 ms] Start: Loading environment from ExecServer
[204 ms] Host OS: linux 4.18.0-513.24.1.el8_9.x86_64
[205 ms] Host CWD: /
[206 ms] Start: Run: /bin/sh 
[259 ms] Start: Run in host: echo ~
[317 ms] /user/antwerpen/203/vsc20380
[317 ms] 
[318 ms] Start: Run in host: id -un
[382 ms] vsc20380
[382 ms] 
[383 ms] Start: Run in host:  (command -v getent >/dev/null 2>&1 && getent passwd 'vsc20380' || grep -E '^vsc20380|^[^:]*:[^:]*:vsc20380:' /etc/passwd || true)
[457 ms] userEnvProbe: loginInteractiveShell (default)
[457 ms] userEnvProbe: not found in cache
[458 ms] userEnvProbe shell: /bin/bash
[2119 ms] userEnvProbe PATHs:
Probe:     '/apps/antwerpen/scripts:/data/antwerpen/203/vsc20380/miniforge3/bin:/data/antwerpen/203/vsc20380/miniforge3/condabin:/user/antwerpen/203/vsc20380/.local/bin:/user/antwerpen/203/vsc20380/bin:/apps/antwerpen/scripts:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin'
Container: None
[2184 ms] Start: Run: uname -m
[2262 ms] Start: Run: /bin/sh (cat /etc/os-release || cat /usr/lib/os-release) 2>/dev/null
[2341 ms] Start: Downloading VS Code Server
[2342 ms] cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba linux-x64 stable
[9729 ms] Start: Extracting tarball
[9731 ms] Start: Run: mkdir -p /user/antwerpen/203/vsc20380/.vscode-remote-containers/bin/cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba_1738738731926
[9843 ms] Start: Run: tar --no-same-owner -x --strip-components 1 -C /user/antwerpen/203/vsc20380/.vscode-remote-containers/bin/cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba_1738738731926
[32223 ms] Start: Run: mv -n /user/antwerpen/203/vsc20380/.vscode-remote-containers/bin/cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba_1738738731926 /user/antwerpen/203/vsc20380/.vscode-remote-containers/bin/cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba
[32452 ms] Initializing configuration support...
[32453 ms] Internal initialization of dev container support package...

Expand log without serverInstallPath set:

[210 ms] Dev Containers 0.394.0 over Remote - SSH 0.116.1 in VS Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba).
[209 ms] Start: Loading environment from ExecServer
[237 ms] Host OS: linux 4.18.0-513.24.1.el8_9.x86_64
[237 ms] Host CWD: /
[238 ms] Start: Run: /bin/sh 
[292 ms] Start: Run in host: echo ~
[333 ms] /user/antwerpen/203/vsc20380
[334 ms] 
[334 ms] Start: Run in host: id -un
[393 ms] vsc20380
[393 ms] 
[394 ms] Start: Run in host:  (command -v getent >/dev/null 2>&1 && getent passwd 'vsc20380' || grep -E '^vsc20380|^[^:]*:[^:]*:vsc20380:' /etc/passwd || true)
[455 ms] userEnvProbe: loginInteractiveShell (default)
[455 ms] userEnvProbe: not found in cache
[456 ms] userEnvProbe shell: /bin/bash
[2050 ms] userEnvProbe PATHs:
Probe:     '/apps/antwerpen/scripts:/data/antwerpen/203/vsc20380/miniforge3/bin:/data/antwerpen/203/vsc20380/miniforge3/condabin:/user/antwerpen/203/vsc20380/.local/bin:/user/antwerpen/203/vsc20380/bin:/apps/antwerpen/scripts:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin'
Container: None
[2239 ms] Initializing configuration support...
[2239 ms] Internal initialization of dev container support package...

Confirmed in both Windows and Fedora Linux for Dev Containers 0.394.0 over Remote - SSH 0.116.1 in VS Code 1.96.4 (and 1.96.2).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers
Projects
None yet
Development

No branches or pull requests

2 participants