Support for vaults in Windows Subsystem for Linux (WSL)

I also created an account to bump this request, Obsidian via WSL2 works but it does not work great. There is a lot of strange issues with apps in WSL that Microsoft might not prioritize fixing anytime soon

+1111

It would be great if the Windows Obsidian could handle the WSL folders natively just like Windows folders.

We are using mdBook to generate documentation in markdown files and store it in our git. Checking it out on wsl2 and being able to use normal terminal commands for committing stuff is helpful. How cool would it be if I can use Obsidian as an editor for my markdown files.

A big +1 from my side. And since this has been a thing since 2020, hopefully it will be implemented soon.

+1 as well

+1, please and thank you <3

Any updates towards this? It’s still an issue and makes using Obsidian difficult. If you don’t have a second GPU then you have to disable GPU acceleration when running Obsidian within WSL due to the virtualization pass-thru not allowing such things.

To chime in here, it appears other apps have had similar issues when trying to run the Windows native app on a WSL path, and the workaround was to set an environment variable to use ‘polling’ rather than the default file watching technique.

Specifically for an app called bruno, the watcher uses chokidar under the hood and one can set the variable CHOKIDAR_USEPOLLING=true to fix this same issue on their app.

I tried to do this by setting the Target field of the shortcut to Windows native WSL to the following:

C:\Windows\System32\cmd.exe /c "SET CHOKIDAR_USEPOLLING=true&& START /D ^"C:\Users\spenc\AppData\Local\Programs\Obsidian^" Obsidian.exe"

and by running Obsidian directly using the embedded subcommand seen in the Target above. I also tested using the \\wsl$\Ubuntu\... and by mounting the network drive to a letter. None of these tests have fixed the issue yet, so I wonder if it’s because Obsidian’s file watcher doesn’t use chokidar and instead we need to set a different variable to enable polling.

I personally would prefer to run Obsidian natively on my computer, but have my files on WSL2 for several reasons which preclude the three other options as listed by @rapatel0.

  • The git strategy I use is unstable/buggy for git for windows (git + git-annex)
  • Native linux git is extremely slow on NTFS, also would be bad trying native git-annex
  • (in other words git has to be WSL2 and files have to be WSL2)
  • Linux native obsidian has a buggy GUI (breaks on tiling using PowerToys FancyZones)
  • Linux native obsidian crashes on certain commands (e.g. Reveal file in explorer via hotkey)

In short, WSL files and native Windows Obsidian is the one path I see for myself, but this fswatcher error is blocking that. A potential path forward I see is enabling polling for the fswatcher. While this is a slower technique and may make large Vaults slower than ideal, it appears to be the only workaround known for watching files from WSL2 mounted on Win11.

I believe they are not willing to fix this. Typora has had no such issue since long time ago.

I have source code repo in Windows WSL2. All docs are in markdown in Docs folder. Would love to manage the markdown files using Obsidian. But I am not able to open the WSL2 folder \\wsl.localhost\Ubuntu-24.04\Proj1 in Obsidian. There are many windows applications that support this.

I’d like to pitch in here, much of the current GenAI related development is done in python, typescript, rust etc and the best way to handle that on Windows is basically in a WSL. Supporting \wsl$ connections would be the simplest way to view my documentation under this setup.

Sad to see this is an open issue since 2020 :frowning:

Hi, I have an app interacting with my vault folder. For now, im just having robocopy do 1:1 and duplicating the folder. So ideally, I write something in my pretty obsidian app, then if i need to go push to git any changes from my vault, i can switch to wsl. Hope this drawing helps someone:

image|515x499

nvm, now looking into syncthing or some other bidirectional sync methods

:herb: Workaround: Obsidian Windows + Ubuntu WSL (Claude Code and Git too)

I struggled with this too. Installing Obsidian on Ubuntu (WSL) really didn’t work for me either. The work around I have is to install Obsidian on Windows but use it still via Ubuntu (WSL). Here’s what I did:

  1. Install Obsidian on Windows and create a vault there
  2. Open the vault folder in VSCode via Remote - WSL, using the `/mnt/c/[wherever you put your vault directory]` path
  3. Claude Code will still be there because you’re in WSL
  4. Also your Ubuntu Git will be there too (it’s just a bit slower to refresh in Source Control View)

Here is a handover I used with Claude Code if it’s useful to anyone:

handover.md (3.3 KB)

New user to Obsidian, went around in circles with this unfortunately. @Michelle99 solution works though! :clap:

Bump :+1:

There are so many comments in this thread, but I don’t think this solution has been posted yet:

Her er en komplet guide klar til at kopiere ind i forumtråden:


:white_check_mark: Working solution: Install Obsidian inside WSL2

This allows Obsidian to open vaults stored in the WSL filesystem directly — no symlinks, no workarounds. WSL2 supports native Linux GUI apps that appear as regular Windows windows (via WSLg).

Requirements

  • Windows 10/11 with WSL2

  • Ubuntu (or Debian-based distro)


Step 1 — Install dependencies

sudo apt-get update
sudo apt-get install -y libasound2t64 wget curl

Note: On Ubuntu 24.04+, the package is libasound2t64 — not libasound2.


Step 2 — Download and install Obsidian

This script always fetches the latest release from GitHub:

LATEST=$(curl -s https://api.github.com/repos/obsidianmd/obsidian-releases/releases/latest \
  | grep -o '"tag_name": "v[^"]*"' \
  | grep -o 'v[^"]*')

VERSION=${LATEST#v}

wget "https://github.com/obsidianmd/obsidian-releases/releases/download/${LATEST}/obsidian_${VERSION}_amd64.deb" \
  -O /tmp/obsidian.deb

sudo apt-get install -y /tmp/obsidian.deb


Step 3 — Launch Obsidian

obsidian

The Obsidian window opens on your Windows desktop. You can now open any vault inside your WSL filesystem (e.g. ~/projects/myvault).


Expected output (harmless warnings)

You may see these on first launch — they are all safe to ignore:

Ignored: Error: ENOENT: no such file or directory, open '...obsidian.json'
ERROR: components/viz/...Exiting GPU process due to errors during initialization

The first warning disappears after you open a vault. The GPU error means Obsidian falls back to software rendering inside WSL — it works fine.


Updating Obsidian later

Just re-run the Step 2 script — it always pulls the latest version.


@stigfaerch This was already proposed, please see the comment by @rapatel0 (link). A tutorial on how to install Obsidian on debian is unfortunately not a solution to this issue. Obsidian in WSL2 has its own issues, as noted by me (link)

Happy almost six years with no movement :frowning:

Remote SSH plugin is working wonderfully in WSL2