Unable to open devcontainers on v1.4.5

Support Bug Reports
1

Describe the Bug

I upgraded cursor this morning and since then I cannot open a devcontainer within cursor. I’ve tried in two different repos and they both fail with:

2025-08-14 09:54:53.395 [info] Spawned process undefined: 'docker' 'info'
2025-08-14 09:54:53.395 [info] [docker info]: Running command: docker
2025-08-14 09:54:53.395 [error] [docker info]: Running command: docker
2025-08-14 09:54:53.396 [error] Error running 'docker info' [docker info] Command failed with exit code 1: spawn docker ENOENT: stdout: 
2025-08-14 09:54:53.396 [error] Failed to reopen folder in container Error running `docker info`. Please ensure docker is installed and running: [docker info] Command failed with exit code 1: spawn docker ENOENT: stdout:

I am able to issue docker info in a separate terminal without issue:

> which docker
/usr/local/bin/docker
> docker info
Client:
 Version:    28.3.2
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
...
...

Steps to Reproduce

  1. Open a repo in cursor that contains a devcontainer
  2. Popup appears with message “This workspace contains a devcontainer.json file. Would you like to reopen it in a container?” I click “Reopen in container”
  3. It fails immediately with error given above.

Expected Behavior

devcontainer should open without error.

Screenshots / Screen Recordings

cursorerror.png
cursorerror.png1235×334 65.6 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.4.5 (Universal)
VSCode Version: 1.99.3
Commit: af58d92614edb1f72bdd756615d131bf8dfa5290
Date: 2025-08-13T02:08:56.371Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 23.6.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

3

Hi @jamiekt, could you try explicitly specifying the docker path in the dev.containers.dockerPath setting?

image
image1808×307 13.3 KB

4

Hi @ravirahman ,

I’v just returned to work after being away for ten days. In that time the problem seems to have alleviated itself. I’ve just tried opening a devcontainer from within Cursor and it has done so successfully. I have not changed dev.containers.dockerPath. I note that the Cursor version has changed from 1.4.5 to 1.5.9:

Version: 1.5.9 (Universal)
VSCode Version: 1.99.3
Commit: de327274300c6f38ec9f4240d11e82c3b0660b20
Date: 2025-08-30T21:02:27.236Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 23.6.0
6

Hi @ravirahman ,

This problem has just started occurring again. Upon trying to open a repo in a devcontainer I’m again getting error

2025-09-23 09:29:46.029 [info] Spawned process undefined: 'docker' 'info'
2025-09-23 09:29:46.029 [info] [docker info]: Running command: docker
2025-09-23 09:29:46.029 [error] [docker info]: Running command: docker
2025-09-23 09:29:46.029 [error] Error resolving dev container authority Failed to check Docker version -- is docker installed and running?: [docker info] Command failed with exit code 1: spawn docker ENOENT: stdout:

image
image1200×208 22.5 KB

Here is the version information

Version: 1.6.45 (Universal)
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 23.6.0

The path to docker is already set explicitly as per your screenshot above, here is the screenshot from mine:

image
image639×283 6.81 KB

Any suggestions?

8

Bumping - same issue here. I am on version 1.7.44

10

@ravirahman STILL a problem. Would really appreciate some advice here please.

11

Cursor likely spawns commands like:

ssh user@host "docker info"

This creates a non-interactive, non-login shell which doesn’t source .zshrc or .bash_profile, so Docker isn’t in the PATH.

adding a dockerPath is ignored for some reason so after i’ve added export PATH=“/Applications/Docker.app/Contents/Resources/bin:$PATH” to my `~/.zshenv` and restarting the cursor tunnel solved the problem