vscode remote desktop user is always "coder"
Hi,
When connecting via VS Code desktop extension, the user is always coder. This means that when connecting to a workspace where we specifically set up a user that has a real username from one of our teams, any files created are not visible, neither are mounted GCS buckets etc.
Am I just missing how to correctly configure the vs code extension to use my coder user account, or is there just not an option for this.
In it's current state, for our use cases, it renders the vscode extension almost entirely useless.
I really hope there is a simple solution here.
Are we the only people using real usernames in the workspaces of our users?
4 Replies
<#1416043216322433188>
Category
Help needed
Product
Coder (v2)
Platform
Linux
Logs
Please post any relevant logs/error messages.
You can always use kustomize or dotfiles modules to properly setup your vscode (also git-config for setting up the authoring configs)
The problem is the remote vs code desktop coder extension as far as I can tell, not vscode in the browser.
Perhaps I didn't explain the issue well enough.
When connecting from VS code on my mac to a workspace in our coder instance via the VS Code Extension, the username that the VS Code extension uses for remote connections is always "coder".
Our workspaces in our coder instance use the real usernames of our users, and therefore the desktop extension does not load the correct home dir of the user in question, it instead creates a new home dir for the "coder" user.
Or perhaps I'm missunderstanding what you're trying to tell me...
Hmm, I think this is actually a vscode issue and nothing to do with the extension.
My apologies for barking up the wrong tree
I'd say that this can be closed