Docker Extension Is Broken in Cursor After Extension Updates

Bug Reports
31

@ravirahman Since I installed anysphere.remote-ssh v. 1.0.8 there is no more issues with killed processes I mentioned before.

Probably, it is better to close this topic and create a new one, but I still have an issue with Remote Explorer. It is not a critical one, but it seems worth it to report it.

I see the following message on Dev Containers section in Remote Explorer tab.

CleanShot 2025-06-13 at 20.53.47
CleanShot 2025-06-13 at 20.53.47357×243 5.44 KB

In logs I see the following:

2025-06-13 20:51:19.588 [error] [ssh_auth_socket][/tmp/cursor-remote-ssh-6fb434c1-4b18-44de-a143-72458301feee.sock] forwarder process stderr: 67,111,110,110,101,99,116,105,111,110,32,101,115,116,97,98,108,105,115,104,101,100,10
2025-06-13 20:51:24.050 [info] Spawned process undefined: 'docker' 'info'
2025-06-13 20:51:24.050 [error] Failed to run `docker info`:Error: [checkVersion] Command failed with exit code 1: spawn docker ENOENT: stdout: 
2025-06-13 20:54:37.948 [error] [ssh_auth_socket][/tmp/cursor-remote-ssh-6fb434c1-4b18-44de-a143-72458301feee.sock] forwarder process stderr: 67,111,110,110,101,99,116,105,111,110,32,101,115,116,97,98,108,105,115,104,101,100,10

I use anysphere.remote-containers v 1.0.6.

If I run docker info in terminal inside my DevContainer it works okay. Here is an output:

docker info
Client:
 Version:    28.1.1-1
 Context:    default
 Debug Mode: true
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  0.24.0-1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.33.1
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 43
  Running: 14
  Paused: 0
  Stopped: 29
 Images: 361
 Server Version: 25.0.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: systemd
 Cgroup Version: 2
 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: a1496014c916f9e62104b33d1bb5bd03b0858e59
 runc version: v1.1.11-0-g4bccb38
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 5.15.0-141-generic
 Operating System: Ubuntu 22.04.3 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 31.12GiB
 Name: ubuntuserver
 ID: ce705e00-a2ae-4ae8-a6d3-e6d5d72326de
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
  File Descriptors: 5099
  Goroutines: 6937
  System Time: 2025-06-13T23:56:34.326659248Z
  EventsListeners: 0
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Out put of the docker version command:

Client:
 Version:           28.1.1-1
 API version:       1.44 (downgraded from 1.49)
 Go version:        go1.23.8
 Git commit:        4eba3773274f9d21ba90ae5bc719c3f1e4bb07a1
 Built:             Fri Apr 18 09:44:47 UTC 2025
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          25.0.1
  API version:      1.44 (minimum version 1.24)
  Go version:       go1.21.6
  Git commit:       71fa3ab
  Built:            Tue Jan 23 23:09:23 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.27
  GitCommit:        a1496014c916f9e62104b33d1bb5bd03b0858e59
 runc:
  Version:          1.1.11
  GitCommit:        v1.1.11-0-g4bccb38
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
33

Hi @am1ter,

Thanks for raising this issue. The view here shows only the local docker containers, even if connected to a Remote SSH host. So, this error means that Docker isn’t installed and running locally (even if it’s set up on your remote host). Realize this is quite confusing, and we’ll fix this in another update.

In the meantime, please use the command palette or the “Containers” view (provided by the MS Container Tools extension) to connect to containers on the remote host – attaching a screenshot:

image
image574×258 14.7 KB

34

@ravirahman Thanks! Got it! I think we can close this thread. Thank you everyone for help here.

35

Hi @am1ter, we just shipped version 1.0.7 of the Remote Containers extension that fixes this – if connected to an SSH host, the remote explorer will now show the containers on the remote (not local) machine.

36

@ravirahman Now everything works good, I don’t see any issues with SSH connections or DevConatiners.

2 Likes