Consider including details on sharing SSH keys for Git in definitions

[Chuxel]

While microsoft/vscode-remote-release#106 is the real fix for this issue, we provide guidance on how to copy SSH keys into your container for use with git here.

We could include a simple script in the base dev containers that execute these steps and a postCreateCommand and mount point in devcontainer.json either by default, or can be un-commented in the mean time.

[Chuxel]

This is no longer needed given we have first class support for SSH agent forwarding.

[PavelSosin-320]

@Chuxel Sorry! Could you explain in the details what is it First-class support?
Do you mean that ssh client and git work via bridge network of the container host? So you have no problems with the host firewall. Is it really independent of the container's network driver? I tried it with the official alpine/git container and it was not too easy.
I also didn't find any documentation about how to inject credentials into the container in a secure manner. I familiar with this issue without storing it in the image and making it available for everybody who can access images or containers via plane docker -H host image/container inspect.

[Chuxel]

See https://code.visualstudio.com/docs/remote/containers#_using-ssh-keys

[zioalex]

Hi @Chuxel , I think this way is not good enough. Not everybody has Administrator access to run the agent on the Windows host.
Please can you provide a good way to copy the ssh key in the container?

At the moment trying to copy it with:
USER vscode
COPY ./ssh_config_dir/id_rsa /home/vscode/.ssh/id_rsa

produce the follow error:

[37057 ms] /bin/sh: 35: cannot create /home/vscode/.ssh/known_hosts: Permission denied
[37057 ms] Exit code 2
[37063 ms] Command in container failed: # Copy C:\Users\S0VP8H\.ssh\known_hosts to /home/vscode/.ssh/known_hosts
(dd iflag=fullblock bs=8192 count=0 2>/dev/null; dd iflag=fullblock bs=7821 count=1 2>/dev/null) >/home/vscode/.ssh/known_hosts

[hpe-ykoehler]

What about ssh "known_hosts"?