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

Unable to add mount for Development Drive attached as Junction #11706

Closed
1 of 2 tasks
MartinSGill opened this issue Jun 18, 2024 · 2 comments
Closed
1 of 2 tasks

Unable to add mount for Development Drive attached as Junction #11706

MartinSGill opened this issue Jun 18, 2024 · 2 comments

Comments

@MartinSGill
Copy link

Windows Version

Microsoft Windows [Version 10.0.22631.3737]

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.146.1-2

Distro Version

Ubuntu-24.04

Other Software

No response

Repro Steps

A lot of existing tooling expects source to be in a certain folder. To benefit from the Dev Drive feature, I create an additional mount in the old, expected folder in c:\

  1. Create a Dev Drive
  2. Mount it a drive (e.g. p:)
  3. Mount it into the filesystem e.g. c:\projects
  4. cd into a directory in c:\projects
  5. type wsl

Expected Behavior

WSL starts in folder /mnt/c/projects/ folder

Actual Behavior

<3>WSL (9499) ERROR: CreateProcessEntryCommon:496: chdir(/mnt/c/Projects) failed 5
and I'm ~

Note: when under p:\ WSL correctly starts in /mnt/p/...

image

Diagnostic Logs

No response

Copy link

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 scipt will output the path of the log file once done.

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:

Closed 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