Configuration Options for Mounting Physical Drive(s) or VHDX(s) when WSL Starts
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
I'd like to start by saying what an awesome development system/tool WSL is. Thank-you for your efforts.
Feature Request
Currently, WSL provides a CLI command for mounting physical disks, VHDXs, etc. This works perfectly fine. However, there are several use cases where it would be useful to automate the mount command by a setting option in the WSL config file(s). This would offer a clean user experience out of the box.
My primary use case is this: I want to have a turnkey solution to setup a VSCode web server as part of my WSL distro which utilizes an independent (from the Linux distro) drive/VHDX setup to store only my source repos (mounted to home/"user name"/src). I can do this all right now, but not in a turnkey way.
Current Alternatives
Using Windows Task Scheduler to start and mount drives for WSL in my opinion is not a good user experience. WSL can be shutdown at any time making solutions complex.
I know that there are closed issues where this feature has been requested, but I thought that I'd bring it up again as many devs have requested this in one form or another.
Thanks in advance!
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.
Research direction
The request concerns the WSL CLI and WSL configuration files; no implementation file or test is named. Start by reviewing how WSL starts and how its existing physical-disk and VHDX mounting command works. Done means a configuration option can mount those drives or VHDXs automatically at startup, including the requested source-repository path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- cli, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100