Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
I’m running Docker inside WSL2, not using Docker Desktop on Windows.
This setup has been working perfectly fine until recently:
I was able to attach to running containers from Cursor without issues.
However, now Cursor fails to attach, while VS Code still works with the exact same setup.
Steps to Reproduce
I just try to attach container cursor
Expected Behavior
Cursor should behave similarly to VS Code Remote / Dev Containers:
Detect and use the WSL environment
Invoke docker inside WSL, not on the Windows host
Allow attaching to containers started in WSL
This used to work previously, so this feels like a regression or a recent internal change in how Cursor resolves Docker.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.2.43 (system setup)
VSCode Version: 1.105.1
Commit: 32cfbe848b35d9eb320980195985450f244b3030
Date: 2025-12-19T06:06:44.644Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100
Does this stop you from using Cursor
Yes - Cursor is unusable
