jnovack / docker-vscode-hack-osx

Work-Around and Discussion for https://github.com/microsoft/vscode-remote-release/issues/24

docker-vscode-hack-osx

Work-Around and Discussion for microsoft/vscode-remote-release#24

2020-02 Update

Upstream Issue 24 has been closed with a work-around until official mainstream support. I am no longer accepting issues or pull-requests since official support will be provided. Please support the original developers. I am archiving this repository for posterity.

Preamble

This repository was made to provide files and instructions for implementing the work-around for VSCode Remote-SSH installation on OSX. Currently, an issue exists tracking an official solution.

Please keep all questions regarding this work-around here in this repository so that the official issue is not clogged like a forum thread.

Please create an Issue here to ask your question. Please check Closed Issues before asking your question.

Instructions

Remote Host

1. Install Docker.
2. Open Terminal
3. mkdir vscode-hack
4. cd vscode-hack
5. vi Dockerfile
6. docker build -t ssh .
7. docker run -d -p 2222:22 --name ssh -v ${HOME}:/opt --restart unless-stopped ssh

Local Host

Within VSCode:

1. Click Remote Explorer
2. Click Settings
3. Edit .ssh/vscode.config

vscode.config

Host OSX
    HostName IP.AD.DR.ESS
    User root
    Port 2222
    StrictHostKeyChecking no
    UserKnownHostsFile=/dev/null

Caveats

Backdoor

Do not be decieved, this is a BACKDOOR into your system. This has not been vetted by a security team, nor is intended to anything more than a "work-around".

• The directory you expose to docker is available for anyone who can figure out or crack your container's password.
• This exposes a default linux container which can run binaries on your remote machine as root. You have been warned.

Catalina Permissions

In the docker run statement above, I am mapping my home directory to /opt on the Remote Host. This may or may not be what you want, depending on your development environment. If you map to /opt, upon first connection, Docker will attempt to enumerate all directories and prompt you for access. If you have mapped to your home directory, Docker may prompt for additional permissions ("Documents", "Desktop", "Downloads", etc) on the remote.

"Docker" would like to access files in your Documents folder.
                           [ Don't Allow ]         [ OK ]

If you click [ Don't Allow ], you will not be able to remotely see files in that folder.