Anywhere Dev container extension bug

Describe the Bug

When I “Dev Containers: reopen in dev container” It prompt this error:
2025-06-29 09:14:36.453 [info] Checking for exec server for remote authority: wsl+ubuntu
2025-06-29 09:14:36.453 [info] Using remote exec server for authority: wsl+ubuntu
2025-06-29 09:14:36.728 [info] Copying devcontainer CLI from c:\Users\XXXXX.cursor\extensions\anysphere.remote-containers-1.0.8\dist@devcontainers to /tmp/devcontainer-cli-1164e75a-d71c-42ff-a8cd-4089c36227d5
2025-06-29 09:14:37.506 [info] Devcontainer CLI written to /tmp/devcontainer-cli-1164e75a-d71c-42ff-a8cd-4089c36227d5
2025-06-29 09:14:43.964 [info] Getting remote exec server for authority: wsl+ubuntu
2025-06-29 09:14:45.187 [info] [docker info][stderr]: WARNING: No blkio throttle.read_bps_device support
2025-06-29 09:14:45.187 [info] [docker info][stderr]: WARNING: No blkio throttle.write_bps_device support
2025-06-29 09:14:45.187 [info] [docker info][stderr]: WARNING: No blkio throttle.read_iops_device support
2025-06-29 09:14:45.187 [info] [docker info][stderr]: WARNING: No blkio throttle.write_iops_device support
2025-06-29 09:14:45.187 [info] [docker info][stderr]: WARNING: daemon is not using the default seccomp profile
2025-06-29 09:14:45.202 [info] docker version: Client:
Version: 26.1.1
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.14.0-desktop.1
Path: /usr/local/lib/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.27.0-desktop.2
Path: /usr/local/lib/docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.29
Path: /usr/local/lib/docker/cli-plugins/docker-debug
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: /usr/local/lib/docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.23
Path: /usr/local/lib/docker/cli-plugins/docker-extension
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.4
Path: /usr/local/lib/docker/cli-plugins/docker-feedback
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.1.0
Path: /usr/local/lib/docker/cli-plugins/docker-init
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /usr/local/lib/docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.8.0
Path: /usr/local/lib/docker/cli-plugins/docker-scout

Server:
Containers: 5
Running: 2
Paused: 0
Stopped: 3
Images: 37
Server Version: 26.1.1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: e377cd56a71523140ca6ae87e30244719194a521
runc version: v1.1.12-0-g51d5e94
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
Kernel Version: 5.15.146.1-microsoft-standard-WSL2
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 15.28GiB
Name: docker-desktop
ID: 3eb24f3b-0881-4263-983f-e7b24962c645
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Labels:
com.docker.desktop.address=unix:///var/run/docker-cli.sock
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
127.0.0.0/8
Live Restore Enabled: false
2025-06-29 09:14:45.203 [info] Searching for devcontainer.json files
2025-06-29 09:14:45.352 [info] Found 1 devcontainer.json files: \home\XXXXX\repo\recengine-platform.devcontainer\devcontainer.json
2025-06-29 09:14:45.352 [info] Reading devcontainer config with command: read-configuration --workspace-folder /home/XXXXX/repo/recengine-platform --config /home/XXXXX/repo/recengine-platform/.devcontainer/devcontainer.json
2025-06-29 09:14:45.352 [error] Failed to read devcontainer config Devcontainer CLI not found at /tmp/devcontainer-cli-1164e75a-d71c-42ff-a8cd-4089c36227d5/cli/dist/spec-node/devContainersSpecCLI.js: EntryNotFound (FileSystemError): /tmp/devcontainer-cli-1164e75a-d71c-42ff-a8cd-4089c36227d5/cli/dist/spec-node/devContainersSpecCLI.js
2025-06-29 09:14:45.353 [error] Failed to reopen folder in container Failed to read devcontainer configuration

Steps to Reproduce

  1. in windows, open project in WSL
  2. fix the devcontainer.json as usual
  3. install Anywhere dev container extension
    4, >Dev container: reopen in dev container
  4. this error happened and could not open

Expected Behavior

Vscode can open as dev container properly with microsoft official dev container extension. Curosor could not.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.6 (user setup)
VSCode Version: 1.96.2
Commit: 5b19bac7a947f54e4caa3eb7e4c5fbf832389850
Date: 2025-06-25T02:20:02.577Z
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

1 Like

It seems cursor try to find anywhere devcontainer cli here but it didn’t find the cli. The Anywhere extension has installed properly

1 Like

Same here since I have replaced microsoft dev containers by anysphere dezv containers… And I can’t install back ms dev containers… It always only show me anysphere

FYI I have abandoned Cursor for my team project and switched to Copilot. Cursor has too many things going on right now. I’ll wait for couple months for them get more stable.

1 Like

Hi @MattWang, thank you for sharing this issue. Which remote WSL extension are you using? If you’re on the VSCode WSL extension inside Cursor, could you try switching to the Anysphere Remote WSL?

Our remote containers extension is not compatible with the VSCode WSL extension. From these logs, it looks like the files might not have copied over as expected.

Thanks for replying. I was using Anywhere WSL as well.
For security reason my team is unable to use open vsix anymore but I’m very happy to try Cursor again with my side projects in the future.