-
Notifications
You must be signed in to change notification settings - Fork 828
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Change WLS to mount at /home path directly #10133
Comments
The |
Thank you @Biswa96, I've read this doc. However, I couldn't find the required steps / setup to ensure that the path resolves directly at Am I missing something? Is this even possible? |
That option in wsl.conf is not related to move or mount |
@CleanHit the
and then
What is the output of |
@elsaco running |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Windows Version
Microsoft Windows [Version 10.0.22621.1702]
WSL Version
1.2.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.90.1
Distro Version
Ubuntu 22.04
Other Software
Linux Docker version 24.0.0, build 98fdcd7
Visual Studio Code 1.78.2
Remote-WSL Extension 0.78.7
Remote Development 0.24.0
Docker image uses Dev Containers 0.288.1 in VS Code 1.77.3
Repro Steps
The process executes a script that I'm not allowed to post here. It invokes docker commands. I have
In my /etc/wsl.conf file.
Expected Behavior
The path in the command
Start: Run: wsl -d Ubuntu-22.04 -e /bin/sh -c cd '/c/home/<path_to_project>' && /bin/sh
should be/home/<path_to_project>
. Without appending/c
prefix to/home
path everything would work.Actual Behavior
I'm using a WSL2 Ubuntu 22.04 container on my Window 11 2H22 machine with systemd enabled and Docker installed inside. When the docker commands get executed, I get:
The script fails because the WSL command appends
/c
prefix to/home
path in the commandStart: Run: wsl -d Ubuntu-22.04 -e /bin/sh -c cd '/c/home/<path_to_project>' && /bin/sh
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: