Anysphere and MS Dev Containers cannot be used!

Bug Reports
1

Describe the Bug

Anysphere’s Dev Containers can only connect to one Docker container, connecting multiple containers will result in an error message:
Failed to install Cursor server: Failed to determine container architecture: Error: [uname -m] Command failed with exit code 127: stdout: OCI runtime exec failed: exec failed: unable to start container process: exec: “uname”: executable file not found in $PATH: unknown.

This will not appear in VSCode。And Dev Containers in MS version cannot connect to Docker on versions greater than cursor 1.0

Steps to Reproduce

.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.4 (user setup)
Commit: 1.96.2
Date: e86fcc937643bc6385aebd982c1c66012c98cae0
Electron: 2025-06-19T02:19:20.052Z
ElectronBuildId: 34.5.1
Chromium: undefined
Node.js: 132.0.6834.210
V8: 20.19.0
OS: 13.2.152.41-electron.0

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hi @abc_csdas, thanks for sharing this issue. Could you share the “Remote - Dev Containers” logs from both containers?

It’s a bit surprising the this uname issue would show up only when both containers are open; could you confirm that both containers open independently?

4

Please add Podman support. Dev Containers seems to specifically rely on Docker.

6

Hi @retticle, we don’t directly support podman. As a workaround, it sounds like you can configure Podman to expose docker-compatible socket (Podman docker compatibility - Nick's Blog and Digital Garden). You can then change (or configure) a Docker context. to use this Podman socket as the docker host. The Anysphere Remote Containers extension uses the currently-selected Docker context.