Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Unable to launch bash prompt using custom wsl.conf root mount path #1538
ConEmu build: 180429 x32
The Spring 2018 stable edition of Windows now supports adding in a wsl.conf file where you can customize the root mount location. It defaults to
Steps to reproduce
ConEmu will fail to load bash because it says wslbridge.exe is not found, and the failing path includes
I went into the ConEmu task settings and went to edit this Bash::bash task:
and still received the same results (I changed the
Is there something else I would need to edit for it to use a different wslbridge path? I was just poking around and changing things in hopes it would work.
A bash terminal prompt to open as it does without a custom
And both help page
Also I do think this is a ConEmu issue.
Because if I change my wsl.conf file to use the
But with ConEmu I see:
This is with using
It's like that bridge path is hard coded to always look in
Try these binaries
It works great now while using
I also logged out of Windows completely to make sure my mounts were clear.
And the output of running
Edit: It's also worth pointing out that my .bashrc has no manual bind mounts happening, so this is definitely working well. Docker for Windows volume mounts also work out of the box.
As I said, this options is used for pasting paths only. Your choice.
Ask this in Microsoft/WSL tracker. May be that is a WSL bug.
So for 100% clarity, I should do something like this if I wanted to goto my
That -new_console flag comes out when I choose the startup dir from your dialog box. But I completely removed the current console flag since it didn't seem to do anything with new console set?