microsoft / vscode-remote-release

Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.

Visual Studio Code Remote Development

Visual Studio Code Remote Development Open any folder in a container, on a remote machine, or in WSL and take advantage of VS Code's full feature set. Learn more!

This repository is for providing feedback on the Visual Studio Remote Development extension pack and its related extensions. You can use the repository to report issues or submit feature requests on any of these extensions:

• Remote - SSH
  • Remote - SSH: Editing Configuration Files
• Dev Containers
• WSL
• Remote - Tunnels and the Visual Studio Code Server.

If you are running into an issue with another extension you'd like to use with the Remote Development extensions, please raise an issue in the extension's repository. You can reference our summary of tips for remote related issues and our extension guide to help the extension author get started.

Issues related to the Dev Container ecosystem may be reported in several places. Issues involving Features, Templates, or Images can be reported in the relevant repo. Issues relating to the open source dev container CLI can be reported on devcontainers/cli. You may use the dev container spec repository to file and review issues to shape the direction of development containers and the dev container CLI.

Documentation

Running into trouble? Wondering what you can do? These articles can help.

• Overview
• Remote Development using SSH
• Developing inside a Container
• Developing in WSL
• Tips, Tricks, and Troubleshooting

Releases

VS Code Remote Development extension "stable" releases are tied directly to VS Code releases. Release highlights can be found in VS Code release notes which will include a link to detailed extension release notes.

The extensions are developed using the same development process and schedule as VS Code itself. You can see what is planned for the current development iteration in a pinned planning issue in this repository. This issue will include a link to the broader VS Code plan. As with VS Code itself, the extensions will update during a development iteration with changes that are only available in VS Code Insiders Edition.

Providing Feedback

You can use this repository to:

• Up-vote a feature or request a new one.
• Search for existing issues already reported for potential workarounds.
• Report a problem if you don't find what you are looking for.

If you have a question, connect with the community using any of these social platforms:

See our CONTRIBUTING guide for more details.

License

By downloading and using the Visual Studio Remote Development extension pack and its related extensions, you agree to the product license terms and privacy statement.

License for this repository:

Copyright © Microsoft Corporation All rights reserved.
Creative Commons Attribution 4.0 License (International): https://creativecommons.org/licenses/by/4.0/legalcode

vscode-remote-release's Issues

_updateEnableProposedApi is called to late for resolvers

The extension services updates the enabledProposedApi flags, e.g based on product.json, but for resolvers that's too late resulting in proposed api usage errors

https://github.com/microsoft/vscode/blob/573db674611aff1420b7b5d627339acd235c95d4/src/vs/workbench/services/extensions/electron-browser/extensionService.ts#L842

Port forwarding issue?!

Hello, I'm not sure if this is an issue of the Remote-Container feature or a networking issue of my local configuration. Sorry beforehand if the problem is mine (I currently can't understand it very well):

I had to run the container manually, with the -p 9000:9000 instead of the automatic-p 127.0.0.1:9000:9000. I couldn't reach the flask server inside the container so I had to make it available to all interfaces... I'm not sure why.

Perhaps someone can explain to me why this happened. Thank you

Search doesn't work after opening a workspace from a dev container

Repo

1. Clone https://github.com/Microsoft/vscode-extension-samples locally
2. Open the folder
3. Run the Reopen in container command. Select the node 8 container
4. Once the folder has been reopened in the container, go to the samples.code-workspace file
5. Click on the open workspace button in that file. The workspace should open (still inside the container)
6. Now try performing a file search

bug
Search fails. In the dev tools console, see the errors:

/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:238 [Extension Host] Error: spawn /root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/node_modules/vscode-ripgrep/bin/rg ENOENT
	at Process.ChildProcess._handle.onexit (internal/child_process.js:229:19)
	at onErrorNT (internal/child_process.js:406:16)
	at process._tickCallback (internal/process/next_tick.js:63:19)
t.log @ /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:238

I talked with @roblourens about this issue and we were not sure what was supposed to happen if you open a workspace this way or if this scenario is supposed to be supported

VS Code server failed to start when changing directory in bash_profile

• VSCode Version: 1.34 Insider
• Local OS Version: Windows 10 1809
• Remote OS Version: N/A (locally using Ubuntu 18.04 for WSL)
• Remote Extension/Connection Type: WSL

Steps to Reproduce:

1. Open a WSL window using "Remote-WSL: New Window"
2. "Installing VS Code Server in WSL: Installing WSL components" fails with this error:

VS Code Server for WSL closed unexpectedly. Check WSL terminal for more details

And here are those details:

[2019-05-02 20:19:51.286] Starting VS Code Server inside WSL.
[2019-05-02 20:19:51.602] Launching C:\WINDOWS\System32\wsl.exe bash -i -c "./scripts/wslServer.sh 473af338e1bd9ad4d9853933da1cd9d5d9e07dc9 insider .vscode-remote  " in c:\Users\User\.vscode-insiders\extensions\ms-vscode-remote.remote-wsl-0.31.0
[2019-05-02 20:19:52.625] bash: ./scripts/wslServer.sh: No such file or directory
[2019-05-02 20:19:52.625] VS Code Server for WSL closed unexpectedly.

Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes

Create Configuration files should add an empty 'postCreateCommand' attribute

For discovery reasons we should add an empty postCreateCommand attribute in the generated devcontainer.json file.

Error: ENOSPC: System limit for number of file watchers reached

Issue Type: Bug

Looks like the Remote - SSH extension, which is brilliant by the way, opens a few fs watchers. A few too many that is.

Edit: I should add I was trying to run Jest with the --watch option.

System: Hyper-V VM running Debian Sid.
Linux Dev 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1 (2019-04-12) x86_64 GNU/Linux

Linux: watcher can produce ENOSPC when too many handles open

Regards @grantcarthew

Extension version: 0.34.0
VS Code version: Code - Insiders 1.34.0-insider (473af338e1bd9ad4d9853933da1cd9d5d9e07dc9, 2019-05-01T00:22:05.899Z)
OS version: Windows_NT x64 10.0.17134
Remote OS version: Linux x64 4.9.0-9-amd64

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz (8 x 2712)
GPU Status	2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: enabled surface_synchronization: enabled_on video_decode: enabled webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	31.86GB (13.27GB free)
Process Argv
Screen Reader	no
VM	0%

Item	Value
Remote	SSH: dev
OS	Linux x64 4.9.0-9-amd64
CPUs	Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz (4 x 2518)
Memory (System)	9.74GB (8.24GB free)
VM	0%

Cannot install on v1.33.1

• VSCode Version: 1.33.1 (user setup)
• Local OS Version: Windows 10
• Remote OS Version: N/A
• Remote Extension/Connection Type: All

Steps to Reproduce:

1. Have VS Code v1.33.1
2. Try to install ms-vscode-remote.vscode-remote-extensionpack or any of it's members

Error received when installing via VS Code marketplace:
"Unable to install because, the extension 'ms-vscode-remote.vscode-remote-extensionpack' compatible with current version '1.33.1' of VS Code is not found."

can not pass env variable values for extension host debugging in WSL

Issue Type: Bug

similar to microsoft/vscode#45423

node v10.6.0
npm 6.1.0
launch.json contents:

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "name": "Launch Program",
            "useWSL": true,
            "runtimeArgs": [
                "--experimental-modules"
            ],
            "env": {
                "SQLITEFILE": "chap07.sqlite3",
                "NOTESMODEL": "sqlite3"
            },
            "program": "${workspaceFolder}\\bin\\www.mjs"
        }
    ]
}

cannot access NOTESMODEL via process.env.NOTESMODEL

VS Code version: Code 1.25.1 (1dfc5e557209371715f655691b1235b6b26a06be, 2018-07-11T15:43:53.668Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item	Value
CPUs	Intel(R) Core(TM) m3-7Y30 CPU @ 1.00GHz (4 x 1608)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: disabled_software video_decode: enabled video_encode: enabled vpx_decode: unavailable_software webgl: enabled webgl2: enabled
Memory (System)	7.89GB (3.72GB free)
Process Argv	C:\Program Files\Microsoft VS Code\Code.exe
Screen Reader	no
VM	0%

Extensions (6)

Extension	Author (truncated)	Version
Handlebars	and	0.4.1
vscode-eslint	dba	1.4.12
mssql	ms-	1.4.0
cpptools	ms-	0.17.6
debugger-for-chrome	msj	4.8.0
html-css-class-completion	Zig	1.17.1

Remote containers: Add flag to disable prompt on start up

I would like to add docker configuration files to my team's extensions so that running and testing these extensions remotely would be easier and more consistent (everyone testing has one spec).

A workspace config setting to disable the Reopen in container message on startup would make the extension less intrusive - I can always 'Open Folder in Container' if I want to. :-)

Please add support for ARM (and Raspberry Pi)

It would be great if VSCode remote would also support connecting to Raspian on a Raspberry Pi.

On Twitter @egamma said, there's no AMD build (yet) for the VS Code server part yet. For Raspian this also needs to be a 32bit build, and not 64bit.

Raspberry Pi 2's all have ARMv6 or ARMv7 CPUs which are all 32bit only, and while Raspberry Pi 3's have an ARMv8 CPU that is 64bit capable, Raspbian is only available in 32bit builds.

Allow a dev container to disable an extension

Feature request
Allow a dev container to specify that a specific extension should not be enabled. As an example use case, projects that use Flow would want to disable the built-in js/ts extension. Maybe using a - prefix:

{
    "extensions": {
       "-vscode.typescript-language-features"
  }
}

Specify remote alternative to /tmp

Some remote machines have /tmp mounted with noexec. Offering an alternative for the end-user to specify a directory such as their own home directory would allow end-users to use this feature w/o needing to remount /tmp

Please support macOS SSH host

There are many scenarios where the development stack lives on macos but we have the need to develop locally on windows or linux. Specifically I am thinking of flutter. cc @DanTup

Remote indicator needs a max length

This is not very good use of screen real estate:

Allow customers to force extensions to be remote/local from the UI

We have a setting right now that will allow people to force extensions onto the workspace or UI side. This is useful for extensions that can run in multiple places (Docker) or for testing.

To improve discoverability of this useful feature, it would be useful to add this into the UI as a "force" option when installing or as a right click gesture that updates settings.json.

//cc: @sandy081 @egamma

Can't connect through jumpbox

Some users may leverage ~/.ssh/config to set up ProxyJump and ProxyCommands to get to their endpoints. Currently, it appears that VSCode Remote only supports a direct connection.

Error setting up container for vscode-remote-try-node: tar "Cannot change ownership to uid 1001, gid 1001: Invalid argument"

Issue Type: Bug

git clone https://github.com/Microsoft/vscode-remote-try-node
code-insider vscode-remote-try-node

VS Code version: Code - Insiders 1.34.0-insider (473af338e1bd9ad4d9853933da1cd9d5d9e07dc9, 2019-05-01T05:15:04.403Z)
OS version: Linux x64 4.19.26-03278-g71dc68f9c9d0
Fetching remote diagnostics for 'Dev Container: Node.js Sample' failed.

System Info

Item	Value
CPUs	06/8e (4 x 1607)
GPU Status	2d_canvas: unavailable_software checker_imaging: disabled_off flash_3d: unavailable_off flash_stage3d: unavailable_off flash_stage3d_baseline: unavailable_off gpu_compositing: unavailable_off multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: unavailable_off surface_synchronization: enabled_on video_decode: unavailable_off webgl: enabled_readback webgl2: unavailable_off
Load (avg)	1, 1, 1
Memory (System)	4.84GB (0.44GB free)
Process Argv	--unity-launch
Screen Reader	no
VM	40%

Fetching remote diagnostics for 'Dev Container: Node.js Sample' failed.

Extensions: none

Logs from Dev Containers terminal:

Setting up container for folder: /home/mhofman/workspace/vscode-remote-try-node
Run: docker build -f /home/mhofman/workspace/vscode-remote-try-node/.devcontainer/Dockerfile -t vsc-vscode-remote-try-node-2fc4d91231746fe94e241abdcb5e6b97 /home/mhofman/workspace/vscode-remote-try-node/.devcontainer
Sending build context to Docker daemon  4.096kB
Step 1/8 : FROM node:lts
lts: Pulling from library/node
e79bb959ec00: Pulling fs layer 
d4b7902036fe: Pulling fs layer 
1b2a72d4e030: Downloading [>                                                  ] d4b7902036fe: Downloading [>           e79bb959ec00: Pull complete 
d4b7902036fe: Pull complete 
1b2a72d4e030: Pull complete d54db43011fd: Pull complete 69d473365bb3: Pull complete 
6e2490ee2dc8: Pull complete 
6381e1b5feaa: Pull complete 
b1efb42c63e2: Pull complete 
Digest: sha256:dbe1830d4a8b5ec8226b1cb4a760f9e53696130f76bd4c2e5785e13eba19993b
Status: Downloaded newer image for node:lts
 ---> 64c810caf95a
Step 2/8 : ENV DEBIAN_FRONTEND=noninteractive
 ---> Running in b738e2773e26
Removing intermediate container b738e2773e26
 ---> a4cd7fda33cc
Step 3/8 : RUN apt-get update    && apt-get -y install --no-install-recommends apt-utils 2>&1
 ---> Running in 092712e92be1
Ign:1 http://deb.debian.org/debian stretch InRelease
Get:2 http://security.debian.org/debian-security stretch/updates InRelease [94.3 kB]
Get:3 http://deb.debian.org/debian stretch-updates InRelease [91.0 kB]
Get:4 http://deb.debian.org/debian stretch Release [118 kB]
Get:5 http://deb.debian.org/debian stretch Release.gpg [2434 B]
Get:6 http://security.debian.org/debian-security stretch/updates/main amd64 Packages [487 kB]
Get:7 http://deb.debian.org/debian stretch-updates/main amd64 Packages [11.1 kB]
Get:8 http://deb.debian.org/debian stretch/main amd64 Packages [7082 kB]
Fetched 7886 kB in 4s (1652 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libapt-inst2.0
The following NEW packages will be installed:
  apt-utils libapt-inst2.0
0 upgraded, 2 newly installed, 0 to remove and 29 not upgraded.
Need to get 602 kB of archives.
After this operation, 1607 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian stretch/main amd64 libapt-inst2.0 amd64 1.4.9 [192 kB]
Get:2 http://deb.debian.org/debian stretch/main amd64 apt-utils amd64 1.4.9 [410 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 602 kB in 0s (2058 kB/s)
Selecting previously unselected package libapt-inst2.0:amd64.
(Reading database ... 29978 files and directories currently installed.)
Preparing to unpack .../libapt-inst2.0_1.4.9_amd64.deb ...
Unpacking libapt-inst2.0:amd64 (1.4.9) ...
Selecting previously unselected package apt-utils.
Preparing to unpack .../apt-utils_1.4.9_amd64.deb ...
Unpacking apt-utils (1.4.9) ...
Setting up libapt-inst2.0:amd64 (1.4.9) ...
Setting up apt-utils (1.4.9) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Removing intermediate container 092712e92be1
 ---> 355d9d1c2ffb
Step 4/8 : RUN apt-get install -y git procps
 ---> Running in c0847c405164
Reading package lists...
Building dependency tree...
Reading state information...
git is already the newest version (1:2.11.0-3+deb9u4).
procps is already the newest version (2:3.3.12-3+deb9u1).
0 upgraded, 0 newly installed, 0 to remove and 29 not upgraded.
Removing intermediate container c0847c405164
 ---> 8747343ae1c1
Step 5/8 : RUN rm -rf /opt/yarn-*     && rm -f /usr/local/bin/yarn     && rm -f /usr/local/bin/yarnpkg     && apt-get install -y curl apt-transport-https lsb-release     && curl -sS https://dl.yarnpkg.com/$(lsb_release -is | tr '[:upper:]' '[:lower:]')/pubkey.gpg | apt-key add - 2>/dev/null     && echo "deb https://dl.yarnpkg.com/$(lsb_release -is | tr '[:upper:]' '[:lower:]')/ stable main" | tee /etc/apt/sources.list.d/yarn.list     && apt-get update     && apt-get -y install --no-install-recommends yarn
 ---> Running in 0b5fba8a435f
Reading package lists...
Building dependency tree...
Reading state information...
curl is already the newest version (7.52.1-5+deb9u9).
Suggested packages:
  lsb
The following NEW packages will be installed:
  apt-transport-https distro-info-data lsb-release
0 upgraded, 3 newly installed, 0 to remove and 29 not upgraded.
Need to get 204 kB of archives.
After this operation, 322 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian stretch/main amd64 apt-transport-https amd64 1.4.9 [171 kB]
Get:2 http://deb.debian.org/debian stretch/main amd64 distro-info-data all 0.36 [5810 B]
Get:3 http://deb.debian.org/debian stretch/main amd64 lsb-release all 9.20161125 [27.1 kB]
Fetched 204 kB in 0s (941 kB/s)
Selecting previously unselected package apt-transport-https.
(Reading database ... 30109 files and directories currently installed.)
Preparing to unpack .../apt-transport-https_1.4.9_amd64.deb ...
Unpacking apt-transport-https (1.4.9) ...
Selecting previously unselected package distro-info-data.
Preparing to unpack .../distro-info-data_0.36_all.deb ...
Unpacking distro-info-data (0.36) ...
Selecting previously unselected package lsb-release.
Preparing to unpack .../lsb-release_9.20161125_all.deb ...
Unpacking lsb-release (9.20161125) ...
Setting up apt-transport-https (1.4.9) ...
Setting up distro-info-data (0.36) ...
Setting up lsb-release (9.20161125) ...
OK
deb https://dl.yarnpkg.com/debian/ stable main
Ign:1 http://deb.debian.org/debian stretch InRelease
Hit:2 http://deb.debian.org/debian stretch-updates InRelease
Hit:3 http://security.debian.org/debian-security stretch/updates InRelease
Hit:4 http://deb.debian.org/debian stretch Release
Get:5 https://dl.yarnpkg.com/debian stable InRelease [13.3 kB]
Get:7 https://dl.yarnpkg.com/debian stable/main all Packages [8545 B]
Get:8 https://dl.yarnpkg.com/debian stable/main amd64 Packages [8545 B]
Fetched 30.4 kB in 1s (15.9 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Recommended packages:
  nodejs
The following NEW packages will be installed:
  yarn
0 upgraded, 1 newly installed, 0 to remove and 29 not upgraded.
Need to get 836 kB of archives.
After this operation, 4997 kB of additional disk space will be used.
Get:1 https://dl.yarnpkg.com/debian stable/main amd64 yarn all 1.15.2-1 [836 kB]
Fetched 836 kB in 0s (1671 kB/s)
Selecting previously unselected package yarn.
(Reading database ... 30133 files and directories currently installed.)
Preparing to unpack .../archives/yarn_1.15.2-1_all.deb ...
Unpacking yarn (1.15.2-1) ...
Setting up yarn (1.15.2-1) ...
Removing intermediate container 0b5fba8a435f
 ---> e5873f755a7a
Step 6/8 : RUN npm install -g eslint
 ---> Running in 26412acb6bba
/usr/local/bin/eslint -> /usr/local/lib/node_modules/eslint/bin/eslint.js
+ [email protected]
added 117 packages from 70 contributors in 14.199s
Removing intermediate container 26412acb6bba
 ---> 61c19227f20f
Step 7/8 : RUN apt-get autoremove -y     && apt-get clean -y     && rm -rf /var/lib/apt/lists/*
 ---> Running in 742e2f0d2696
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 29 not upgraded.
Removing intermediate container 742e2f0d2696
 ---> 817ff03cbcc8
Step 8/8 : ENV DEBIAN_FRONTEND=dialog
 ---> Running in ce2cec44b65f
Removing intermediate container ce2cec44b65f
 ---> 6722d877db03
Successfully built 6722d877db03
Successfully tagged vsc-vscode-remote-try-node-2fc4d91231746fe94e241abdcb5e6b97:latest
Run: docker run -a STDOUT -a STDERR -p 127.0.0.1:3000:3000 -v /home/mhofman/workspace/vscode-remote-try-node:/workspaces/vscode-remote-try-node -v /home/mhofman/.gitconfig:/root/.gitconfig -l vsch.quality=insider -l vsch.local.folder=/home/mhofman/workspace/vscode-remote-try-node -l vsch.remote.devPort=9753 vsc-vscode-remote-try-node-2fc4d91231746fe94e241abdcb5e6b97 /bin/sh -c echo Container started ;  while sleep 1; do :; done
Container started
Run: docker exec 6787d41355ad7fbbda7965952da1abf9255962ead20f8b6cad9e74615fcc81f7 /bin/sh -c (cat /etc/os-release || cat /usr/lib/os-release) 2>/dev/null
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
Run: docker exec 6787d41355ad7fbbda7965952da1abf9255962ead20f8b6cad9e74615fcc81f7 test -d /root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9
Installing VS Code Server for commit 473af338e1bd9ad4d9853933da1cd9d5d9e07dc9
Run: docker exec 6787d41355ad7fbbda7965952da1abf9255962ead20f8b6cad9e74615fcc81f7 mkdir -p /root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9_1556834419438
Run: docker cp /tmp/vsch/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/vscode-server-linux-x64.tar.gz 6787d41355ad7fbbda7965952da1abf9255962ead20f8b6cad9e74615fcc81f7:/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9_1556834419438
Run: docker exec -w /root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9_1556834419438 6787d41355ad7fbbda7965952da1abf9255962ead20f8b6cad9e74615fcc81f7 tar -xf vscode-server-linux-x64.tar.gz --strip-components 1
tar: package.json: Cannot change ownership to uid 1001, gid 1001: Invalid argument
...
tar: Exiting with failure status due to previous errors
Command failed: docker exec -w /root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9_1556834419438 6787d41355ad7fbbda7965952da1abf9255962ead20f8b6cad9e74615fcc81f7 tar -xf vscode-server-linux-x64.tar.gz --strip-components 1

Failed to establish connection to remote SSH host

I've been experimenting with the new remote development extension since I heard because it is the thing I've been most excited about for VS Code!

I have a similar environment as #15 and #36 where the remote development environment is a secured i.e. no or very select outside access. So I expect to not be able to properly set up the remote ssh server as eventually it will need to access the marketplace domains.

However I think I am experiencing another error before I get to that point. After attempting to connect, I get this in the remote extension log:

SSH Resolver called for "ssh-remote+wipml01"
SSH Resolver called for host: wipml01
Setting up SSH remote "wipml01"
Using commit id "473af338e1bd9ad4d9853933da1cd9d5d9e07dc9" and quality "insider" for server
Install and start server if needed
> Pseudo-terminal will not be allocated because stdin is not a terminal.
> 
>          IMPORTANT NOTICE
>          ----------------
> 
> 
> 
> Use of this equipment and access to or use of any of the Company's computing or network facilities is subject to <company name>'
> s Corporate Security and Use Policies. Copies of these policies can be obtained by telephoning or online 
> 
> The company reserves the right to monitor, audit, or filter any e-mail, computer hardware or software, or network facilities as requi
> red, in order to enforce this policy. By logging on to this system you agree to comply with these policies and consent to any such mo
> nitoring, auditing or filtering.
> 
> 
> Enter passphrase for key 'C:\Users\ya006948\.ssh\id_rsa':
> 
> 
> bash: cannot set terminal process group (51108): Inappropriate ioctl for device
> bash: no job control in this shell
> 
> bash: /tmp/tmp.jM6fSydug6/vscode-remote-install.473af338e1bd9ad4d9853933da1cd9d5d9e07dc9.sh: Permission denied
> 
"install" terminal command done
Received install output: bash: /tmp/tmp.jM6fSydug6/vscode-remote-install.473af338e1bd9ad4d9853933da1cd9d5d9e07dc9.sh: Permission denied
Failed to parse remote port from server output: bash: /tmp/tmp.jM6fSydug6/vscode-remote-install.473af338e1bd9ad4d9853933da1cd9d5d9e07dc9.sh: Permission denied

I'm not really sure what the issue might be. It looks like there are some permission issues, however the /tmp directory on the remote host has permission bits set to drwxrwxrwt, which seems very permissive. The other thing that seems to be an issue is the

> bash: cannot set terminal process group (51108): Inappropriate ioctl for device
> bash: no job control in this shell

Initially, I had oh-my-zsh as the default login shell but I disabled that as I thought it might be an issue but I get the same results with default bash login shell. I don't really know enough about the remote server implementation to pinpoint much further than this. Hopefully someone can point me in the right direction to getting past this point in the remote vs code server setup and I can fail on the inability to connect to extension marketplace.

• VSCode Version: Insiders 1.34
• Local OS Version: Windows 10 1709 (OS build 16299.1087)
• Remote OS Version: CentOS 7.6.1810
• Remote Extension/Connection Type: SSH
• SSH Client: installed from git for windows.

Steps to Reproduce:

1. Click Remote SSH: connect to host...
2. Select host defined in ssh config in %USERPROFILE%\.ssh\config
3. vs code terminal window opens prompting for identity file password, input password
4. A new vs code window opens, also opening a terminal window and asking for identity file password.
5. vs code server remote server begins installing as evidenced by notification in lower right hand corner
6. Error window with Could not establish connection to <hostname>

Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes

can't install extension pack

Can't install. Clicked on the "install" button of the extension-pack here - extension was opened in the stable VS code version, not in the insiders version (both are installed on my Windows 10 machine). Tried to search for the extension manually from my insiders version, but the extension pack is not found (tried "remote development", "vscode-remote-development", etc.). How can I go about installing it?

Some extension don't show Install in container although they are

See the Install button of the TSLint extension:

and now the one of better search

In the viewlet it is not marked to be installed in the container. It is in the extension editor.

FISH Support

Issue Type: Bug

Will not install/initialize if the shell being used is fish

Extension version: 0.34.0
VS Code version: Code - Insiders 1.34.0-insider (473af338e1bd9ad4d9853933da1cd9d5d9e07dc9, 2019-05-01T00:21:48.884Z)
OS version: Darwin x64 18.5.0
Remote OS version: Linux x64 4.15.0-1037-aws

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-7920HQ CPU @ 3.10GHz (8 x 3100)
GPU Status	2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: enabled rasterization: enabled surface_synchronization: enabled_on video_decode: enabled webgl: enabled webgl2: enabled
Load (avg)	1, 1, 1
Memory (System)	16.00GB (3.95GB free)
Process Argv
Screen Reader	no
VM	0%

Item	Value
Remote	SSH: Jake-VSCode
OS	Linux x64 4.15.0-1037-aws
CPUs	AMD EPYC 7571 (4 x 2199)
Memory (System)	15.53GB (12.56GB free)
VM	0%

Does not work with LCOW

• VSCode Version: insiders
• Local OS Version: Microsoft Windows [Version 10.0.17763.437]
• Remote OS Version: does not matter
• Remote Extension/Connection Type: Docker

Steps to Reproduce:

1. Use Docker for Windows with Windows containers
2. Pull a Linux version, i.e. docker pull --platform=linux node:12.
3. Use that image on your remote settings
4. Try to open the folder remotely

When you try to open the folder it fails. This is related to moby/moby#35425
You get an error invalid mount config for type "bind": source path must be a directory. because of the .gitconfig file from HOME.

Does this issue occur when you try this locally?: N/A
Does this issue occur when you try this locally and all extensions are disabled?: N/A

Parse "Match Host" from ssh config

My /home/user/.ssh/config file looks like this:

Host static
    Hostname some.remote.site
    User kyle
    ControlMaster auto
    ControlPath  ~/.ssh/sockets/%r@%h-%p
    ControlPersist  600

Match Host home exec "nc -w 1 -z 192.168.X.X 22"
    Hostname 192.168.X.X
    User kylrth
    ControlMaster auto
    ControlPath  ~/.ssh/sockets/%r@%h-%p
    ControlPersist  600

Match Host home !exec "nc -w 1 -z 192.168.X.X 22"
    Hostname other.remote.site
    User kylrth
    ControlMaster auto
    ControlPath  ~/.ssh/sockets/%r@%h-%p
    ControlPersist  600

I have a computer at home where I do my work, and when I'm at home I'd like to log in with the local IP address. Outside my home network, I want to use a dynamic DNS site. As such, the configuration used when I run ssh home will depend on whether 192.168.X.X is listening on port 22. When I run Remote SSH: Connect to Host..., the only configuration I see is static. I'd like to see home listed there.

Cannot install on remote if default shell is tcsh

• VSCode Version: 1.34.0-insider
• Local OS Version: macOS Mojave
• Remote OS Version: Red Hat Enterprise Linux Server release 7.6 (Maipo)
• Remote Extension/Connection Type: SSH

Steps to Reproduce:

1. Run 'Remote-SSH: Connect to Host'
2. Specify Remote that uses tcsh as the default shell
3. Observe that the Remote is connected - a new window opens
4. Installation fails with the following:

SSH Resolver called for "ssh-remote+my-host"
SSH Resolver called for host: my-host
Setting up SSH remote "my-host"
Using commit id "473af338e1bd9ad4d9853933da1cd9d5d9e07dc9" and quality "insider" for server
Install and start server if needed
> Warning: no access to tty (Bad file descriptor).
> Thus no job control in this shell.
> INSTALL_SCRIPT=/tmp/tmp.kUk4quopx4/vscode-remote-install.473af338e1bd9ad4d9853933da1cd9d5d9e07dc9.sh: Command not found.
> INSTALL_SCRIPT: Undefined variable.
"install" terminal command done
Received install output: INSTALL_SCRIPT: Undefined variable.
Failed to parse remote port from server output: INSTALL_SCRIPT: Undefined variable.

Does this issue occur when you try this locally?: N/A - issue with connecting
Does this issue occur when you try this locally and all extensions are disabled?: N/A

To me, it looks like an issue with trying to run the script in tcsh (setting a variable in tcsh is set INSTALL_SCRIPT=/path/to/script.csh, for example).

Kubernetes container

Support for containers running in kubernetes (pod, deployment etc..)

Remote file picker input can backtrack while holding the delete key

repo

1. Open a remote folder (tested with containers and wsl)
2. Open remote file open dialog
3. Start at the end of the path and hold the delete key

Bug
While deleting, a segment of deleted path will sometimes be restored

Resolvers are running even if they are disabled

• Open a remote window (WSL or SSH or Dev Container) - I used SSH.
• Disable the respective remote extension (SSH)
• Reload the window
  🐛 SSH connection is established

Allow custom PATH for using newer git version from /usr/local/git

Allow custom PATH for using newer git version from /usr/local/git

I have updated git on the system but using custom path via .bashrc and .profile files from /usr/local/git but vscode keeps using default system git.

Allow a way to define custom PATH for listening agent to use.

user environment variables are not loaded

Issue Type: Bug

User environment variables are not loaded, making most processes not work (RVM doesn't work for example)
DOCKER_HOST is not set
DATABASE_HOST is also not set

Extension version: 0.32.0
VS Code version: Code - Insiders 1.34.0-insider (473af338e1bd9ad4d9853933da1cd9d5d9e07dc9, 2019-05-01T00:22:05.899Z)
OS version: Windows_NT x64 10.0.17763
Remote OS version: Linux x64 4.4.0-17763-Microsoft

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-7Y75 CPU @ 1.30GHz (4 x 1608)
GPU Status	2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: enabled surface_synchronization: enabled_on video_decode: enabled webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	15.89GB (5.29GB free)
Process Argv
Screen Reader	no
VM	0%

Item	Value
Remote	WSL
OS	Linux x64 4.4.0-17763-Microsoft
CPUs	Intel(R) Core(TM) i7-7Y75 CPU @ 1.30GHz (4 x 1601)
Memory (System)	15.89GB (5.29GB free)
VM	0%

Switching between docker-compose dev containers volume mounts the old folder

• VSCode/OS Version:

Version: 1.34.0-insider (user setup)
Commit: c1abf7978d59415dcfcf8cfcb15e0ee30c5e45a5
Date: 2019-04-26T13:39:29.623Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

Steps to Reproduce:

1. Clone and open the app at https://github.com/Microsoft/python-sample-tweeterapp in a dev container
2. After it opens, close it
3. Open the containers/python-3-postgres folder in the https://github.com/Microsoft/vscode-dev-containers repo in a dev container

Instead of seeing the files in the python-3-postgres folder, you instead see the tweeterapp files:

After re-building the container the python-3-postgres files appear:

Both use a similar docker-compose file with services named app and db.

Default shell not launched in remote

If your default shell is not bash it will still launch bash in the terminal. If I open VS Code in Windows and configure the default terminal is WSL it will launch zsh.

• VSCode Version: 1.34.0-insider
• Local OS Version: 10.0.18362 N/A Build 18362
• Remote OS Version: WSL Ubuntu 18 - Linux DESKTOP-GR5DSKM 4.4.0-18362-Microsoft #1-Microsoft Mon Mar 18 12:02:00 PST 2019 x86_64 x86_64 x86_64 GNU/Linux
• Remote Extension/Connection Type: WSL

Steps to Reproduce:

1. Launch WSL with a user who uses a shell other than bash as their default shell (eg: zsh)
2. Launch VS Code
3. Open VS Code terminal
4. See that the shell is bash not the default for the user

Does this issue occur when you try this locally?: Yes.
Does this issue occur when you try this locally and all extensions are disabled?: Yes

Don't remove extension output channels when the EH goes down

• Connect to SSH remote
• Go offline long enough that we stop trying to reconnect
• When we decide that the remote EH is gone, we take down all EHs
• When the local EH goes down, we get rid of all extension output channels
• So then I can't see the ssh output channel and that can make it hard to understand some reconnection issues

If some extension crashes the EH it would also be useful to see its logs, so this seems like a generally useful thing to do.

Support opening Dev Containers when running from within WSL or SSH

This was the first scenario presented to me at PyCon:

Insiders on Windows (for now)
F1, Select Default Shell -> WSL
Open a terminal inside VS Code, you get the WSL shell on /mnt/c/...
git clone a repo with a .devcontainer folder (and Dockerfile, etc.)
cd into the folder and reopen with code-insiders .

The folder is opened in WSL, which makes sense.

However, what if I want to actually open the folder in a container? The expectation was that I would get the prompt to reopen the folder in the container.

To work around this, I would have to go to a cmd shell or power shell and do the clone/open from there. But, I'm simply using the WSL terminal as my default terminal everywhere on Windows, so this is unnatural.

//cc: @sptramer

Show New SSH window command also in the SSH status bar commands contribution

Show the SSH: New window on active host command also in status bar commands menu

Source repo?

Where is the source code repository for the remote extension?

Include "Open devcontainer.json" action in problems resulting from devcontainer.json

When using an "alpine" image in my devcontainers.json I was getting this helpful warning:

After dismissing it this not-so-helpful QuickPick showed up:

I suggest to add an action to "Open devcontainer.json" in the first alert.

Does not support agent forwarding - committing on remote host via SSH fails

• VSCode Version: Version 1.34.0-insider (1.34.0-insider)
• Local OS Version: Mac OS X Mojave 10.14.4 (18E226)
• Remote OS Version: Ubuntu Linux 18.04
• Remote Extension/Connection Type: SSH

Steps to Reproduce:

1. Open remote folder/project workspace with git repository via SSH
2. Try to commit something to an even more remote repo (say GitHub) that relies on SSH auth.

Since the remote server does not have your SSH key and the VS Code connection does not use agent forwarding, key validation by the Git server (GitHub in this case) fails because the remote machine cannot talk to your local SSH agent and does not have valid keys.

This is a breaking issue for anyone who has to work via jump boxes.

Does this issue occur when you try this locally?: N/A
Does this issue occur when you try this locally and all extensions are disabled?: N/A

Remote fails if WSL executes TMUX by default

• VSCode Version: 1.34.0-insider
• Local OS Version: Windows 10, 18351.26
• Remote OS Version: Ubuntu 18.04
• Remote Extension/Connection Type: WSL

Steps to Reproduce:

1. Install tmux in WSL
2. Add "exec tmux" to .bashrc and reload shell (may not have to do the reload since Code starts new session)
3. Install remote extension, if not already installed
4. Run "code-insiders ." in WSL

Code launches and tries to start up the remote connection, but fails with "open terminal failed: not a terminal" and "VS Code Server for WSL closed unexpectedly."

`machine` scope settings defined in user settings need to be ignored in the remote context

When a machine scoped setting is defined in a user setting, then it needs to be ignored in a remote context.

VS Code server failed to start using zsh

• VSCode Version: 1.34.0-insider (user setup)
• Local OS Version: Windows 10 1809
• Remote OS Version: N/A (locally using Ubuntu 18.04 for WSL)
• Remote Extension/Connection Type: WSL (Ubuntu 18.09)

Steps to Reproduce:

1. Launch wsl from powershell
2. open a python folder with virtualenv activated
3. launch code-insiders .

Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes

Use brackets in the `Remote` settings title

Repo

1. Open a dev container
2. Open settings

Bug
The Remote tab title unders settings uses parens to delineate the remote name. In most other places in the UI we use brackets for this:

Allow customization of $PATH for Building Docker Container

If you are pulling Docker images from the Google Container Registery, you need gcloud installed, which on many systems is installed by default at ~/google-cloud-sdk/bin/docker-credential-gcloud.

This path is obviously not in the path by default. It seems that VS Code is not following any rc file for terminals to initialize a custom path. It would be nice if there was a good way to specify the PATH that gets used (if their already is, let me know can close out the ticket).

Extension packs are not installed on correct location

• Open a remote window
• Look for an extension pack that has workspace extensions. Eg: PHP Extension Pack
  🐛 It shows a button install locally
  Expected to show Install on remote

🐛 Clicking on Install, installs PHP extensions locally.
Expected to install remotely

ProxyCommand SSH config not working

• VSCode Version: 1.34.0 (insiders)
• Local OS Version: Windows 10 (1809)
• Remote OS Version: CentOS Linux 7 (Core)
• Remote Extension/Connection Type: SSH

I'm trying to connect to hostB (that's not the real host name, of course), however, it's only accessible after connecting to hostA. To accomplish this, I created the following SSH config file:

Host hostA
    HostName hostA.location.edu
    User bryan
Host hostB
    ProxyCommand ssh hostA.location.edu -W %h:%p
    HostName hostB.location.edu
    User bryan

Executing ssh hostB in my local terminal successfully connects to hostB (localhost -> hostA -> hostB), however, connecting to hostB via the remote-ssh extension yields the following error:

Steps to Reproduce:

1. Create a SSH config file following the localhost -> hostA -> hostB paradigm.
2. ssh hostB via the terminal and observe the jump working properly.
3. Connect to hostB via remote-ssh in vscode and observe the error shown above.

Cannot install on a server without internet access

Our servers are running in a very secure enterprise environment and they don't allow outbound connections to the internet. I had to manually transfer the server package and rig the script to install it.

It would be great if VSCode could just SCP the server package into the server instead of using wget.

Use VS Code Remote Development w/o marketplace, update connectivity

Is there anyway to get around this limitation "VS Code Server requires outbound HTTPS (port 443) connectivity to update.code.visualstudio.com and marketplace.visualstudio.com"?

To clarify: will this work if the local os and remote machine both have ssh connectivity to each other but no outbound connectivity?

Revisit/test extension recommendations

Need to revisit/check strong recommendations. For example, if I open a python file on a remote box without having the python extension installed then I should see the recommendation even if I have declined the recommendation for the local machine.

Windows Server Support

After spending a few hours getting OpenSSH to work with pubkey authentication (Microsoft's guide is 💩), I was excited to finally give this a shot. Then I get the error that only Linux or WSL servers are supported.

So it'd be great for that support to be added.

But in the meantime please try pointing out, in a bigger and much easier to find notification, that Windows isn't supported yet in this manner.

Thanks!

Use Docker for remote linting

We can use Docker for remote debugging; it would be awesome to be able to use Docker for remote linting as well. The idea of getting away from having to install requirements locally is superb!

Determine install folder from within the container

• VSCode Version: 1.34.0-insider
• Local OS Version: macOS Mojave
• Remote OS Version: Debian Stretch
• Remote Extension/Connection Type: Docker

Steps to Reproduce:

1. Create Dockerfile with user different than root

RUN usermod -u 1020 application
USER application

2. Run container
3. Run Remote Containers: Attach to running container...
4. Select container you want to attach to
5. Setup process fails with the following error:

Setting up container with 575f427ee0eab56f3e140dda2aabd89fd80a2e7ab48795e0532d728e73694333
Run: docker exec 575f427ee0eab56f3e140dda2aabd89fd80a2e7ab48795e0532d728e73694333 /bin/sh -c (cat /etc/os-release || cat /usr/lib/os-release) 2>/dev/null
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
Run: docker exec 575f427ee0eab56f3e140dda2aabd89fd80a2e7ab48795e0532d728e73694333 test -d /root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9
Installing VS Code Server for commit 473af338e1bd9ad4d9853933da1cd9d5d9e07dc9
Run: docker exec 575f427ee0eab56f3e140dda2aabd89fd80a2e7ab48795e0532d728e73694333 mkdir -p /root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9_1556829785420
mkdir: cannot create directory ‘/root’: Permission denied
Command failed: docker exec 575f427ee0eab56f3e140dda2aabd89fd80a2e7ab48795e0532d728e73694333 mkdir -p /root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9_1556829785420

That's because the user specified in Dockerfile can't create directories in /root. Is there a way for vscode to select different path than /root/.vscode-remote?