WSL2 CLI fails when Windows Yaak Desktop is running (SQLite disk I/O error)
ImprovementQuestion
When Yaak Desktop is running on Windows, the Yaak CLI inside WSL2 fails with the following error:
Error: Failed to initialize database: Database error: timed out waiting for connection: disk I/O error
Closing the Windows desktop app resolves the issue.
The WSL2 CLI accesses the same SQLite database as the Windows app, which may cause cross-platform locking issues with SQLite WAL mode.
Expected behavior:
Windows GUI and WSL2 CLI should work simultaneously while sharing the same workspace data.
Could this be fixed without requiring separate databases?
Windows2026.9.0
Thanks for the clear report. The cause is SQLite’s write-ahead log: it relies on shared memory for its lock file, and that doesn’t work across the WSL2 to Windows file-system bridge, so a Linux process and a Windows process can’t safely open the same database. Sharing one database across that boundary isn’t something Yaak can fix on its own side.
The practical way to share the workspace is to run the Windows build of the CLI from inside WSL2 (Windows executables run from a WSL shell), which goes through the same locking as the desktop app. Does that work for your setup?