Devcontainer users struggle to open the right workspace
VS Code devcontainer users want the correct .code-workspace file to open automatically, but its location may not line up with the devcontainer configuration. One user reports symlinking files into a generated workspace directory as a workaround, while others ask how to automate opening the workspace and whether the requested setting will be implemented. A separate request for containers per workspace directory points to an adjacent, broader multi-root workflow problem.
For developers using VS Code devcontainers. Mentioned from Sep 2019 to Mar 2022 on GitHub.
3 different people described this problem in 2 separate discussions.
- Indie fit
- 2.0/10
- Pain
- 5.0/10
- Frequency
- 5.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Right now I'm symlinking the needed files in a generated workspace file's directory, but that seems kind of hacky (details here)
Did you ever figure out how to auto open a code-workspace file when the devcontainer opens?
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks