-
Notifications
You must be signed in to change notification settings - Fork 282
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.
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
[Remote-SSH Bug]: failed to create symbolic link #7853
Comments
Hello! I am seeing the error |
Remote-SSH Log
From vscode terminal:
|
sorry for the delay- I'm going to attempt to repro. Thanks |
Hello! It looks like this is a duplicate of this issue, there seem to be some suggestions on what fixes might be on here as well as a discussion on issues/ status. Thanks |
@eleanorjboyd I don't think these issues are related. I can confirm that in my setup vscode server side is running under |
Is there an existing issue for this bug?
Debugging Steps
remote.SSH.useLocalServer
setting->
No response
Versions
Expected Behavior
In my setup when I ssh to a remote server my user is changed to
admin
(this is pretty common practice in many organizations). The last line in my user's.zshrc
is/usr/bin/sudo --preserve-env /bin/su admin
. In order to run vscode asadmin
user and be able to edit files I addedRemoteCommand /usr/bin/sudo --preserve-env /bin/su admin
to ssh config file.The problem is that I can't use vscode to push to remote git. This is because vscode tries to create ssh auth socket under my original user instead of admin. Here is the output from vscode terminal:
Because auth socket is not created, git can't access my private key via ssh-agent forwarding.
Steps To Reproduce
No response
Remote-SSH Log
Remote-SSH Log
Anything else?
No response
The text was updated successfully, but these errors were encountered: