No gpg-agent running (or killed?) when connecting to a devcontainter through a tunnel

[daantimmer]

• VSCode Version: 1.98.0 (user setup)
• Local OS Version: Windows_NT x64 10.0.19045
• Remote OS Version: Ubuntu 24.04
• Remote Extension/Connection Type: Dev Containers/Remote - Tunnels/VS Code Server
• Logs:
  • vscode-tunnel-server-log.txt
  • vscode-tunnel-client-log.txt

Steps to Reproduce:

1. start vscode on remote machine, enabling tunnel service
2. start devcontainer on remote machine
3. test for gpg --list-secret-keys

• observe that a key exists

4. start devcontainer through tunnel from a client machine
5. test for gpg --list-secret-keys on the vscode server machine

• observe that there are no more keys. Command fails with: gpg: can't connect to the gpg-agent: End of file

6. test for gpg --list-secret-keys on the vscode client machine

• osserve that there are no more keys. Command fails with: gpg: can't connect to the gpg-agent: End of file

Does this issue occur when you try this locally?: No, if I don't use a tunnel, then everything works fine.
Does this issue occur when you try this locally and all extensions are disabled?: Works locally already, no need to disable extensions

Screenshot of gpg --list-secret-keys

[chrmarti]

The log shows that Dev Containers attempts to forward GPG to the remote host:

gpg-agent: Socket in container (/root/.gnupg/S.gpg-agent) forwarded to remote host (C:\Users\[redacted]\AppData\Local\gnupg\S.gpg-agent.extra).

It also runs the following to work around an issue on Mac:

Start: Run: gpg-connect-agent updatestartuptty /bye