microsoft / microsoft/vscode-remote-release
Support shared home folder
Open
@chrmarti is already working on this.
Since Feb 1, 2025.
containers
feature-request
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
- VSCode Version: 1.96.4
- Local OS Version: Fedora 41 (Kinoite)
- Remote OS Version: Ubuntu 24.04.1 LTS
- Remote Extension/Connection Type: Dev Containers - VS Code Server
- Logs: log.log
Steps to Reproduce:
encountered while following https://prismlauncher.org/wiki/development/build-instructions/linux/
- create ubuntu distrobox with
distrobox create --image ubuntu:latest --name prism; distrobox enter prism - run
Dev Containers: Attach to Running Containerand chooseprism
[761 ms] Command in container failed: mkdir -p /home/scarf/.vscode-server/bin/cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba_1738434099427
[761 ms] mkdir: cannot create directory '/home/scarf/.vscode-server': File exists
scarf@fedora /r/m/h/s/r/e/o/PrismLauncher (develop)> lsd -alh ~/.vscode-server
lrwxrwxrwx. scarf scarf 23 B 2024-09-28 토 00:20:36 /home/scarf/.vscode-server ⇒ /var/tmp/.vscode-server
scarf@fedora /r/m/h/s/r/e/o/PrismLauncher (develop)> lsd -alh /var/tmp/.vscode-server
lsd: /var/tmp/.vscode-server: No such file or directory (os error 2).
maybe it's because it's symlinked? what's weird is i was already attaching an existing distrobox with vscode and this is the second container where i get this error.
Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: Yes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.