microsoft
Custom remote installation directory for Containers
#472 added an option to chose a custom directory to place the .vscode-server directory in SSH remote targets. #940 had the same question for Containers but got closed as a duplicate so I can't comment there/reopen it. They're not the same, and similar options for remote Containers would be really handy.
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!
leaving this comment here as well as 6837
Hi @chrmarti, so I realized that the InstallPath for the dev-container is still not configurable. The custom path for installing vscode-server on a remote machine is extremely valuable.
The scenario is as follows: 1-ssh into a remote machine on vscode(with custom InstallPath) 2-attach to running docker container. Here, the dev container vscode-server appears to default to the original home directory(prior to step 1), which in my case, negates the benefits of step 1.
Would it possible to provide such flexibility soon?
When I start a devcontainer as remoteUser "ezdev" (on local machine), the vscode-server keeps getting installed in /root.... why is it not respecting the remoteUser setting and installing vscode-server in /home/ezdev instead ?
Start: Run in container: test ! -f '/root/.vscode-server/data/Machine/.writeMachineSettingsMarker' && set -o noclobber && mkdir -p '/root/.vscode-server/data/Machine' && { > '/root/.vscode-server/data/Machine/.writeMachineSettingsMarker' ; } 2> /dev/null mkdir: cannot create directory '/root': Permission denied Exit code 1
Is this expected behaviour ?
Having a devcontainer with a workspaceMount type=bind at $HOME leaves your workspaceFolder always with lots of trash directories (vscode-remote, .dotnet, etc.) which are then unnecessarily tracked by git and use lots of file watcher's file descriptors leaving you with Unable to watch for file changes error.
It would be perfect to create a docker volume at chosen location and point vscode to install all its server files there.
