Sharing SSH keys broken agent in 1.101.0 Windows 11 x64

[gremo]

Does this issue occur when all extensions are disabled?: N/A because I don't know if they are needed in order to share SSH keys

• VS Code Version: 1.101.0
• OS Version: Windows 11 x64

Before this update, I was able to open a project in my Dev Container and work via SSH. However, after the update, SSH suddenly stopped working.

Investigating further:

root@b9d191e5709a:/app# ssh-add -l
Could not open a connection to your authentication agent.

Agent is of course running on my host machine. Rebuilding without cache didn't help.

EDIT: Reverted back to 1.100.3 and it works fine again:

root@de79f8108af9:/app# ssh-add -l
<redacted> Marco@PC-MARCO (RSA)

[MiikaH]

I'm also having the same issue on Windows 11 24H2:

SSH Agent in a Dev Container works with previous VSCode version (1.100.3) but doesn't work with the latest version (1.101.0).

[szucsz]

the SSH_AUTH_SOCK environment variable is not exposed inside the container when running on vscode version 1.101.0. On the previous version it is defined when devcontainer starts and points to SSH_AUTH_SOCK=/tmp/vscode-ssh-auth-343149b9-54b7-4706-92f3-0a38a2924fce.sock

[marcedal]

exactly same issue here.

I am trying as temporary workaround to define manually the SSH_AUTH_SOCK env variable to one of the latest created sockets, but no luck so far.

[gruvy245]

I have the same issue on 1.101.0 when using WSL Ubuntu 24.04. This is not an issue when using WSL Ubuntu 20.04. Downgrading to 1.100.3 fixes it for WSL Ubuntu 24.04

[neilenns]

Spent an entire day trying to figure out why on both my desktop and laptop I couldn't use 1password with my devcontainers anymore. Sure enough, it seems like it's this issue. SSH_AUTH_SOCK isn't set in the devcontainer.

Rolling back to 1.100.3 fixed it.

[xCykrix]

Spent an entire day trying to figure out why on both my desktop and laptop I couldn't use 1password with my devcontainers anymore. Sure enough, it seems like it's this issue. SSH_AUTH_SOCK isn't set in the devcontainer.

Rolling back to 1.100.3 fixed it.

Exact issue with 1Password as well. Going to try this too, thought I was going insane. Lots of issues with this in VSCode of the last few weeks.

[neilenns]

Exact issue with 1Password as well. Going to try this too, thought I was going insane. Lots of issues with this in VSCode of the last few weeks.

Make sure you disable auto update in settings, otherwise VS code will auto update in the background and the next time you launch you will wonder why 1password is broken again.

Don't ask me how I know this.

[joshspicer]

Thanks for reporting. Please share your environment details when commenting - it sounds like a lot of folks on Windows using SSH + then a nested form of remote from there (WSL/Dev Containers). Please share if your environment differs.

I will try a https://github.com/microsoft/vscode-bisect to see if I can understand the responsible commit here in VS Code. (There was no Remote - SSH release this past month). If you're also able to bisect in an affected environment, please do share the results.

Lastly, I'd appreciate any Remote - SSH and Dev Container logs for extra hints