microsoft / microsoft/vscode-remote-release
[devcontainers] Warn users using Docker Desktop on Linux
@chrmarti is already working on this.
Since Mar 12, 2024.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
- VSCode Version: Any
- Local OS Version: Any
- Remote OS Version: Any
- Remote Extension/Connection Type: Containers
- Logs: N/A
Steps to Reproduce:
- Try to open any Dev container with Docker Desktop for Linux as the backend
Does this issue occur when you try this locally?: N/A
Does this issue occur when you try this locally and all extensions are disabled?: N/A
This is more of a Docker Desktop on Linux issue, but wanted to mention it here because I feel like maybe VS Code should issue a warning about it? Even repos to test dev containers like vscode-remote-try-node will not work, as Docker Desktop on Linux has an interesting file sharing conundrum. All the files in the container become owned by root, and cannot be edited. A workaround of setting containerUser and/or remoteUser as root might not be a great idea. Maybe if VS Code detects that a Linux user is using Docker Desktop, it should warn about this, proposing some actions to take. Honestly though, who uses Docker Desktop on Linux? 😄
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.