Is cursor going to keep breaking dev container on every single update?!

Support Bug Reports
1

Describe the Bug

Every single time, every single time Cursor does an update the remote dev containers break. every time with different errors. It’s so damn frustrating.

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting “/run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/847c042b10537e0eed1ba8d50b55810202f9b34866514caad4c7656658894164” to rootfs at “/tmp/vscode-wayland-d864f0f5-c0c4-421e-89d5-9237785041b9.sock”: create mountpoint for /tmp/vscode-wayland-d864f0f5-c0c4-421e-89d5-9237785041b9.sock mount: cannot create subdirectories in “/var/lib/docker/rootfs/overlayfs/…”: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

Steps to Reproduce

Connect to a dev container and it just doesn’t work after every update from

Expected Behavior

Be able to connect to dev containers easily and fast on every update.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.3.0 (user setup)
VSCode Version: 1.99.3
Commit: 410000a83355c025daba0c6156955bf08687d080
Date: 2025-07-23T05:57:24.496Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Sorry about this - sending to dev team

4

Hi @mehdi, thank you for sharing this issue. Would you be able to share the full logs?

It’s hard to tell, but my guess is that we are trying to resolve that mountpoint from the Windows side. Could you try to first open a WSL window and then attach to your de container from within WSL (so we’ll resolve it from the Linux side?)

5

Thanks for the reply. The full logs has tons of internal info that I can’t share but I had to fix it quick and I was able to resolve it by changing the mounts in devcontainer.json to an empty array which will disable the mountpoints.

Here is the big problem in general: Cursor forces its updates and the update are quite frequent and ofcourse its based on VS code. and almost every single version has something wrong with dev containers. Dev containers being a very important part of developer day to day needs to be part of the testing of each release at Cursor. I am spending more time figuring out these dev container situations more than actually getting work done on my work.

{
“name”: “${localWorkspaceFolderBasename} py3-pgvector”,
“dockerComposeFile”: “docker-compose.yml”,
“service”: “app”,
“workspaceFolder”: “/workspaces/${localWorkspaceFolderBasename}”,
“forwardPorts”: [8080, 5432, 1025, 8025, 465, 4443],
“mounts”: ,
“customizations”: {
“vscode”: {
“extensions”:
}
}
}