Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Elegantly mount additional virtual hard disks in WSL2 #12333

Closed
pignoi opened this issue Dec 2, 2024 · 2 comments
Closed

Elegantly mount additional virtual hard disks in WSL2 #12333

pignoi opened this issue Dec 2, 2024 · 2 comments

Comments

@pignoi
Copy link

pignoi commented Dec 2, 2024

Problem discription.
When using WSL2 to mount an additional virtual disk, it often requires entering multiple commands before startup. Although the method provided here allows for a one-liner solution, the additional steps can be quite frustrating when debugging and frequently restarting WSL2.

Currently, my solution is to add a script to the Windows startup items. This script first mounts the disk I want and also ensures that the WSL2 distribution runs in the background, allowing me to run some background tasks. However, the problem is that when the distribution is restarted, the disk is not mounted again. Perhaps I could add this script to the $PATH, but that would require changing many of my habits and might lead to issues with mounting the disk multiple times.

set ws=wscript.CreateObject("wscript.shell")
ws.run "wsl --mount --vhd E:\virtual_disks\wsl_data.vhdx --bare", 0
ws.run "wsl -d Ubuntu2404", 0

Solution I'd like
A more elegant implementation is to add the default virtual or physical disks to the .wslconfig file. This is because when you enter wsl --mount --vhd <disk>/<path>, it applies to all distributions by default. Similarly, the settings in the .wslconfig file will apply to all distributions as well. While this may not be a particularly complex solution, it can significantly reduce repetitive work or unnecessary errors.

@pignoi pignoi added the feature label Dec 2, 2024
Copy link

github-actions bot commented Dec 2, 2024

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant