Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

No GPG forwarding if using a remote container from within WSL2 #3191

Closed
mattford63 opened this issue Jun 15, 2020 · 3 comments
Closed

No GPG forwarding if using a remote container from within WSL2 #3191

mattford63 opened this issue Jun 15, 2020 · 3 comments
Assignees
@chrmarti
Labels
bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers *duplicate Issue identified as a duplicate of another issue(s)

Comments

@mattford63
Copy link

Version: 1.47.0-insider (user setup)
Commit: 0288447572790f983c350905bd1fc5b754970a0a
Date: 2020-06-15T07:44:14.223Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19041

  • Remote Extension/Connection Type: SSH/Docker/WSL2

No SSH or GPG forwarding if using a remote container from within WSL2.

Steps to Reproduce:

  1. From within WSL2 navigate to a repo with a .devcontainer.
  2. Launch with code .
  3. Switch to remote container.

It seems the .ssh and .gpg files aren't copied or sockets setup.

SSH on WSL using the Windows ssh-agent or to remote machines works as expected.
@github-actions github-actions bot added the containers Issue in vscode-remote containers label Jun 15, 2020
@RyanTheAllmighty
Copy link

RyanTheAllmighty commented Jun 18, 2020 •
edited
Loading

Can also confirm I'm seeing this issue. Going from Windows directly to Remote Container works fine, but from WSL2 to the same container doesn't work.

While I can work around this for now by not going through WSL2, it's not ideal as file mounting is not fast between Windows and Docker with WSL2

@chrmarti
Copy link
Contributor

Tracking SSH forwarding with WSL2 as #2925.

@chrmarti chrmarti self-assigned this Jun 19, 2020
@chrmarti chrmarti added the bug Issue identified by VS Code Team member as probable bug label Jun 19, 2020
@chrmarti chrmarti changed the title No SSH or GPG forwarding if using a remote container from within WSL2 No GPG forwarding if using a remote container from within WSL2 Jun 19, 2020
@chrmarti
Copy link
Contributor

chrmarti commented Aug 3, 2020 •
edited
Loading

Fixed with #2925. Tested with the pinentry program in WSL configured to use the Gpg4win pinentry, ~/.gnupg/gpg-agent.conf:

pinentry-program "/mnt/c/Program Files (x86)/Gpg4win/bin/pinentry.exe"

#3053 has a few instructions for testing.

@chrmarti chrmarti closed this as completed Aug 3, 2020
@chrmarti chrmarti added the *duplicate Issue identified as a duplicate of another issue(s) label Aug 3, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Sep 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@chrmarti chrmarti

Labels
bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mattford63 @RyanTheAllmighty @chrmarti