-
Notifications
You must be signed in to change notification settings - Fork 35.4k
Closed
Labels
feature-requestRequest for new features or functionalityRequest for new features or functionalityinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insiderson-testplanworkbench-cliVS Code Command line issuesVS Code Command line issuesworkbench-os-integrationNative OS integration issuesNative OS integration issues
Milestone
Description
- VSCode Version: 1.44.2
- Local OS Version: Ubuntu 18.04.4 LTS
- Remote OS Version: Debian Buster (10.3)
- Remote Extension/Connection Type: Docker
Steps to Reproduce:
- Open a terminal in host machine
- Start an ssh-agent by
eval $(ssh-agent -s)
- Add a key (key1) using
ssh-add ~/.ssh/id_ed25519_key1
- Open VS Code from the same terminal
code .
- Run
ssh-add -l
in VS Code terminal (shows the identity of key1) (:+1: ) - Open folder in Remote Container
- Run
ssh-add -l
in VS Code terminal (shows the identity of key1) (:+1: ) - Open another terminal in host machine
- Start a new ssh-agent by
eval $(ssh-agent -s)
- Add a key (key2) using
ssh-add ~/.ssh/id_ed25519_key2
- Open VS Code from the same terminal
code .
- Run
ssh-add -l
in VS Code terminal (shows the identity of key2) (:+1: ) - Open folder in Remote Container
- Run
ssh-add -l
in VS Code terminal (shows the identity of key1) (:-1: )
VS Code somehow only forwards the first ssh-agent to remote container eventhough it has the correct ssh-agent forwarded locally. Am I missing any configuration? Can this be fixed with any settings in devcontainer.json?
Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: N/A
Metadata
Metadata
Assignees
Labels
feature-requestRequest for new features or functionalityRequest for new features or functionalityinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insiderson-testplanworkbench-cliVS Code Command line issuesVS Code Command line issuesworkbench-os-integrationNative OS integration issuesNative OS integration issues