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.

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

[Dev Containers] Add remote.SSH.serverInstallPath equivalent for Dev Containers #9432

Closed
ntessman-capsule opened this issue Jan 24, 2024 · 6 comments
Labels
containers Issue in vscode-remote containers feature-request Request for new features or functionality

Comments

@ntessman-capsule
Copy link

ntessman-capsule commented Jan 24, 2024

There is the remote.SSH.serverInstallPath setting for Remote - SSH, but no way to change where Visual Studio is installed when attaching to containers. This makes it impossible to attach VSCode to containers where home permissions are restricted.

I am referring specifically to the "Attach Visual Studio Code" menu item when right clicking a Kubernetes pod in the Clusters extension window. It will attempt (and fail) to install to the home directory.

@vscodenpa vscodenpa added the containers Issue in vscode-remote containers label Jan 24, 2024
@ggcr
Copy link

ggcr commented Mar 7, 2024

I do not know if that's your case but by creating a symbolic link between my home path and the desired path I was able to overcome this issue.

mkdir -p /your/desired/path/.vscode-remote-containers
ln -s /your/desired/path/.vscode-remote-containers /home/<user>/.vscode-remote-containers

Note that your desired path should be the same as where your .vscode-server is.

This is a solution but Microsoft devs should add this as a setting :(

@ntessman-capsule
Copy link
Author

The issue is that it never creates the remote container folder in the first place, because the SSH user doesn't have permission to create folders in the home directory. I can create folders in other directories, but not the one VSCode wants to use.

A setting to change the destination folder would resolve this issue.

@leon-v
Copy link

leon-v commented Nov 7, 2024

I'd like this too.
I'm currently using VSCode containers to develop within the Home Assistant docker container, but every time Home Assistant updates, the home directory (and my VSCode customisations) are deleted.
I want to be able to set the VSCode server path to be within the Home Assistant config directory so it will be preserved after the container image is replaced.

@bamurtaugh bamurtaugh added the feature-request Request for new features or functionality label Dec 13, 2024
@vs-code-engineering vs-code-engineering bot added this to the Backlog Candidates milestone Dec 13, 2024
Copy link

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 10 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

Copy link

This feature request has not yet received the 10 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding

Copy link

🙁 In the last 60 days, this feature request has received less than 10 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
containers Issue in vscode-remote containers feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

5 participants