microsoft / microsoft/vscode-remote-release
Automate the copy of ~/.ssh/config and ~/.ssh/*.pub from the host to the container
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
This should solve the problem that the ssh client inside the container is not providing the right ssh credentials (when multiple credentials are added to the host ssh-agent). See: https://github.com/microsoft/vscode-remote-release/issues/5026
- This process should be done as currently is been done for
~/.ssh/known_hosts. - Ideally there should be a setting for the container and user pair (see: #3279 about overlaying
devcontainer.json). - As, for now, this is not possible, the config setting should be allowed both as a user (for all containers for this user) and
devcontainer.json(for all users of this container) setting. You should be able to choose with one to use.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the requested ~/.ssh/config and ~/.ssh/*.pub handling with the existing ~/.ssh/known_hosts process. Review devcontainer.json configuration and issue #3279, then confirm how user-level and container-level settings should be selected. Done means the chosen configuration makes the required SSH credentials available inside the container without changing the other setting source.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, vscode
- Domain
- developer-experience, devops, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100