Cursor functionalities fail when attaching to remote Docker container

Describe the Bug

I can successfully connect to the remote SSH machine, and all Cursor functionalities work fine in that context. However, when I attach to a running Docker container on the remote machine, Cursor features stop working:

The Git section remains stuck at:
“Scanning folder for Git repositories…”
The chat does not respond and stays in “planning next moves” until it eventually stops.

With Cursor version 2.0.77, things seem to work as expected. The issue only appears after upgrading to 2.2.20.

Steps to Reproduce

Connect to remote SSH machine via Cursor.
Attach to a running Docker container on the remote machine.
Try using Cursor features (Git panel, chat, etc.).

Expected Behavior

Cursor should work normally inside the attached container (Git integration, chat responses, etc.), as it does in version 2.0.77.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Cursor: 2.2.20
Remote SSH Extension: 1.0.35
Dev Containers Extension: 1.0.29

Additional Information

Environment:

Local Machine: Ubuntu 24.04.3 LTS
Remote SSH Machine: Ubuntu 20.04.6 LTS
Docker Container: Ubuntu 24.04.1 LTS
Kernel: Linux x64 6.14.0-37-generic

Remote SSH machine log

2025-12-16 13:26:31.062 [info] [execServer][spawn] command: docker, args: info, options: {}
2025-12-16 13:26:31.063 [info] [forwarding][multiplex][127.0.0.1:33745 -> 127.0.0.1:35173][2a98f06f-d2ba-4dcf-a0e4-d167276c2f4d] received connection request
2025-12-16 13:26:31.063 [info] [command][4a3af753-b935-48bd-9a3b-66c308374f15] Sending command request: {"command":"docker","args":["info"],"env":{},"token":"76fc1520-2064-45ca-bda7-e932cf65dac4","id":"4a3af753-b935-48bd-9a3b-66c308374f15"}
2025-12-16 13:26:31.065 [info] [forwarding][multiplex][127.0.0.1:33745 -> 127.0.0.1:43937 -> 127.0.0.1:35173][2a98f06f-d2ba-4dcf-a0e4-d167276c2f4d] socks forwarding established
2025-12-16 13:26:31.158 [info] [command][4a3af753-b935-48bd-9a3b-66c308374f15] Process exited with code 0
2025-12-16 13:26:31.159 [info] [execServer][spawn] command: docker, args: ps,--format,{{.Names}}	{{.Image}}	{{.ID}}, options: {}
2025-12-16 13:26:31.159 [info] [forwarding][multiplex][127.0.0.1:33745 -> 127.0.0.1:43937 -> 127.0.0.1:35173][2a98f06f-d2ba-4dcf-a0e4-d167276c2f4d] socks connection closed
2025-12-16 13:26:31.159 [info] [command][4a3af753-b935-48bd-9a3b-66c308374f15] Socket close event received
2025-12-16 13:26:31.160 [info] [forwarding][multiplex][127.0.0.1:33745 -> 127.0.0.1:35173][5c31806a-897f-45bd-8053-84223d0ac2ae] received connection request
2025-12-16 13:26:31.160 [info] [command][f855fc43-8431-471a-9e60-9f83c9e2598d] Sending command request: {"command":"docker","args":["ps","--format","{{.Names}}\t{{.Image}}\t{{.ID}}"],"env":{},"token":"76fc1520-2064-45ca-bda7-e932cf65dac4","id":"f855fc43-8431-471a-9e60-9f83c9e2598d"}
2025-12-16 13:26:31.161 [info] [forwarding][multiplex][127.0.0.1:33745 -> 127.0.0.1:43937 -> 127.0.0.1:35173][5c31806a-897f-45bd-8053-84223d0ac2ae] socks forwarding established
2025-12-16 13:26:31.201 [info] [command][f855fc43-8431-471a-9e60-9f83c9e2598d] Process exited with code 0
2025-12-16 13:26:31.202 [info] [command][f855fc43-8431-471a-9e60-9f83c9e2598d] Socket close event received
2025-12-16 13:26:31.202 [info] [forwarding][multiplex][127.0.0.1:33745 -> 127.0.0.1:43937 -> 127.0.0.1:35173][5c31806a-897f-45bd-8053-84223d0ac2ae] socks connection closed
2025-12-16 13:26:37.420 [info] [tunnel] disposing of tunnel (remote) 127.0.0.1:44317 -> (local) localhost:44317
2025-12-16 13:26:37.420 [info] [tunnel-forwarding]localhost:44317 -> 127.0.0.1:44317] server closed
2025-12-16 13:26:37.420 [info] [tunnel-forwarding]::1:44317 -> 127.0.0.1:44317] server closed
2025-12-16 13:26:37.420 [error] [tunnel] server threw an error when closing Server is not running.
2025-12-16 13:26:59.287 [info] [tunnel-forwarding][localhost:33897 -> 127.0.0.1:33897] server listening
2025-12-16 13:26:59.288 [info] Cross binding to [::1]:33897. Originally bound to 127.0.0.1:33897
2025-12-16 13:26:59.288 [error] [tunnel-forwarding] server threw an error A system error occurred (listen EAFNOSUPPORT: address family not supported ::1:33897)

Remote - Dev Containers log

2025-12-16 13:26:35.581 [info] No remote exec server found for authority: dev-container+7b2273657474696e6754797065223a22636f6e7461696e6572222c22636f6e7461696e65724964223a22396163386135643964333665227d@ssh-remote+7b22686f73744e616d65223a22616d6269742d7562753134227d; using local
2025-12-16 13:26:36.290 [info] Resolving dev container authority 'dev-container+7b2273657474696e6754797065223a22636f6e7461696e6572222c22636f6e7461696e65724964223a22396163386135643964333665227d' (attempt #1) container '{"settingType":"container","containerId":"9ac8a5d9d36e"}'
2025-12-16 13:26:36.290 [info] Using exec server from resolve options. execServerRemoteAuthority: ssh-remote+7b22686f73744e616d65223a22616d6269742d7562753134227d
2025-12-16 13:26:36.308 [info] Starting Dev Containers dev-container+7b2273657474696e6754797065223a22636f6e7461696e6572222c22636f6e7461696e65724964223a22396163386135643964333665227d
2025-12-16 13:26:36.310 [info] [docker info]: Running command: docker
2025-12-16 13:26:36.320 [info] Copying devcontainer CLI from /home/myusername/.cursor/extensions/anysphere.remote-containers-1.0.29/dist/@devcontainers to /tmp/devcontainer-cli-4a605bf9-98a2-40e3-8797-1a3957895793
2025-12-16 13:26:36.387 [info] Devcontainer CLI written to /tmp/devcontainer-cli-4a605bf9-98a2-40e3-8797-1a3957895793
2025-12-16 13:26:36.395 [info] Copying forwarder.js to /tmp/devcontainer-cli-4a605bf9-98a2-40e3-8797-1a3957895793
2025-12-16 13:26:36.410 [info] [docker info][stderr]: WARNING: No swap limit support
2025-12-16 13:26:36.413 [info] [docker info]: Command completed with exit code 0
2025-12-16 13:26:36.413 [info] docker version: Client: Docker Engine - Community
 Version:    27.1.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.16.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.1
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 11
  Running: 8
  Paused: 0
  Stopped: 3
 Images: 11
 Server Version: 27.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 nvidia runc
 Default Runtime: nvidia
 Init Binary: docker-init
 containerd version: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41
 runc version: v1.1.13-0-g58aa920
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
 Kernel Version: 5.4.0-190-generic
 Operating System: Ubuntu 20.04.6 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 96
 Total Memory: 1008GiB
 Name: aitmb-ubu14
 ID: bc520951-41df-4083-919b-fd094f1d3776
 Docker Root Dir: /local/volume1/var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  blablabla.mydomain.com:5000
  10.1.2.100:80
  10.1.0.100:5000
  127.0.0.0/8
 Live Restore Enabled: false
2025-12-16 13:26:36.414 [info] Inspecting docker container 9ac8a5d9d36e (fallback name: myusername_ubu24_dev_docker)
2025-12-16 13:26:36.415 [info] [docker inspect]: Running command: docker
2025-12-16 13:26:36.454 [info] Copying devcontainerShutdownMonitor.js to /tmp/devcontainer-cli-4a605bf9-98a2-40e3-8797-1a3957895793
2025-12-16 13:26:36.471 [info] [docker inspect][stderr]: Error: No such object: 9ac8a5d9d36e
2025-12-16 13:26:36.475 [error] [docker inspect]: Running command: docker
2025-12-16 13:26:36.475 [info] Failed to find container by ID 9ac8a5d9d36e: [docker inspect] Command failed with exit code 1: stdout: []

2025-12-16 13:26:36.475 [info] Attempting to find container by name: myusername_ubu24_dev_docker
2025-12-16 13:26:36.477 [info] [docker container]: Running command: docker
2025-12-16 13:26:36.526 [info] [docker container]: Command completed with exit code 0
2025-12-16 13:26:36.527 [info] Found single container with name myusername_ubu24_dev_docker, using ID: 11d586e93f54
2025-12-16 13:26:36.528 [info] [docker inspect]: Running command: docker
2025-12-16 13:26:36.566 [info] [docker inspect]: Command completed with exit code 0
2025-12-16 13:26:36.582 [info] Getting config for image 10.1.2.100:80/rttt/dev-docker:ubu24.04-th2.7.1-latest from vscode-userdata:/home/myusername/.config/Cursor/User/globalStorage/anysphere.remote-containers/imageConfigs/10.1.2.100%253A80%252Frttt%252Fdev-docker%253Aubu24.04-th2.7.1-latest.json
2025-12-16 13:26:36.592 [info] No container configuration file found for image vscode-userdata:/home/myusername/.config/Cursor/User/globalStorage/anysphere.remote-containers/imageConfigs/10.1.2.100%253A80%252Frttt%252Fdev-docker%253Aubu24.04-th2.7.1-latest.json Unable to read file 'vscode-userdata:/home/myusername/.config/Cursor/User/globalStorage/anysphere.remote-containers/imageConfigs/10.1.2.100%3A80%2Frttt%2Fdev-docker%3Aubu24.04-th2.7.1-latest.json' (Error: Unable to resolve nonexistent file 'vscode-userdata:/home/myusername/.config/Cursor/User/globalStorage/anysphere.remote-containers/imageConfigs/10.1.2.100%3A80%2Frttt%2Fdev-docker%3Aubu24.04-th2.7.1-latest.json')
2025-12-16 13:26:36.597 [info] Getting config for container myusername_ubu24_dev_docker from vscode-userdata:/home/myusername/.config/Cursor/User/globalStorage/anysphere.remote-containers/nameConfigs/myusername_ubu24_dev_docker.json
2025-12-16 13:26:36.601 [info] No container configuration file found for container myusername_ubu24_dev_docker Unable to read file 'vscode-userdata:/home/myusername/.config/Cursor/User/globalStorage/anysphere.remote-containers/nameConfigs/myusername_ubu24_dev_docker.json' (Error: Unable to resolve nonexistent file 'vscode-userdata:/home/myusername/.config/Cursor/User/globalStorage/anysphere.remote-containers/nameConfigs/myusername_ubu24_dev_docker.json')
2025-12-16 13:26:36.601 [info] Returning config: {}
2025-12-16 13:26:36.601 [info] Found attached container configuration: {}
2025-12-16 13:26:36.602 [info] Installing remote server in container...
2025-12-16 13:26:36.602 [info] Reading .gitconfig from /home/myusername/.gitconfig
2025-12-16 13:26:36.611 [info] Stat: {
  "type": 1,
  "size": 308,
  "mtime": 1765874540000,
  "ctime": 0
}
2025-12-16 13:26:36.619 [info] Reading known hosts from /home/myusername/.ssh/known_hosts
2025-12-16 13:26:36.627 [info] Stat: {
  "type": 1,
  "size": 2684,
  "mtime": 1764690334000,
  "ctime": 0
}
2025-12-16 13:26:36.638 [info] Final extension list: 
2025-12-16 13:26:36.641 [info] Install options: {
  "id": "27b7b49dda3330792ec61439",
  "commit": "b3573281c4775bfc6bba466bf6563d3d498d1070",
  "line": "production",
  "extensionIds": [],
  "envVariables": [],
  "serverApplicationName": "cursor-server",
  "forceReinstall": false,
  "killRunningServers": false,
  "realCommit": "b3573281c4775bfc6bba466bf6563d3d498d1074",
  "serverDataFolderName": ".cursor-server",
  "cursorVersion": "2.2.20",
  "spin": false,
  "settings": {},
  "gitConfig": "[user]\n\temail = [email protected]\n\tname = My Name\n[core]\n\ttrustctime = false\n[credential]\n\thelper = \"!f() { /home/myusername/.vscode-server/bin/848b80aeb52026648a8ff9f7c45a9b0a80641e2e/node /tmp/vscode-remote-containers-9cd2c243-34e3-4a81-90c2-0fdafd0266ae.js git-credential-helper $*; }; f\"\n",
  "sshKnownHosts": "|1|CiZYWK0zjn5vvFkKDXys5BF8npM=|NTxTy2PDjRRP6CQ7gZQtWGjgQ/Q= ssh-ed25519 r46DjIK7nT4VWg1H5lBs=|2R217AYgDg64tin09e7/5YFN6wM= ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBG3HEN1po6xkiKiG1Ig54Lw9tx7gVUSGJMvhQo=\n|1|wkcz5kfxdxwyEoh3wpIb/0uuoDI=|ls6VuFje1lBEm33c0DEypbcng3Q= ssh-ed25519 AAAAC3NzaC1lZqMqqIgbqnmSI+U+uNul/aBmDCBMEdDoo\n|1|RpSo4cRNiX+KPpfsB9ihXi8YjlU="
}
2025-12-16 13:26:36.644 [info] Installing server...
2025-12-16 13:26:36.798 [info] [server install] stdout: Waiting for lock...

2025-12-16 13:26:36.800 [info] [server install] stdout: Lock acquired, proceeding with installation.

2025-12-16 13:26:36.801 [info] [server install] stdout: Server script already installed in /home/myusername/.cursor-server/bin/b3573281c4775bfc6bba466bf6563d3d498d1070/bin/cursor-server

2025-12-16 13:26:36.825 [info] [server install] stdout: Server script is already running /home/myusername/.cursor-server/bin/b3573281c4775bfc6bba466bf6563d3d498d1070/bin/cursor-server

2025-12-16 13:26:36.834 [info] [server install] stdout: Git config already exists in container, or no host config found.Skipping git config copy and validation.

2025-12-16 13:26:36.844 [info] [server install] stdout: 27b7b49dda3330792ec61439: start
exitCode==0==
listeningOn==39909==
connectionToken==8bff94a4-22f3-46fa-8c71-a6ea8ef6b028==
logFile==/home/myusername/.cursor-server/.b3573281c4775bfc6bba466bf6563d3d498d1070.log==
arch==x86_64==
remoteServerNodePath==/home/myusername/.cursor-server/bin/b3573281c4775bfc6bba466bf6563d3d498d1070/node==
platform==linux==
27b7b49dda3330792ec61439: end

2025-12-16 13:26:36.845 [info] Finished installing remote server in container. Parsing output...
2025-12-16 13:26:36.845 [info] Result map: {
  "exitCode": "0",
  "listeningOn": "39909",
  "connectionToken": "8bff94a4-22f3-46fa-8c71-a6ea8ef6b028",
  "logFile": "/home/myusername/.cursor-server/.b3573281c4775bfc6bba466bf6563d3d498d1070.log",
  "arch": "x86_64",
  "remoteServerNodePath": "/home/myusername/.cursor-server/bin/b3573281c4775bfc6bba466bf6563d3d498d1070/node",
  "platform": "linux"
}
2025-12-16 13:26:36.845 [info] Server install command exit code: 0
2025-12-16 13:26:36.845 [info] Registering label formatter for dev-container*
2025-12-16 13:26:36.851 [info] [server install]: exit
2025-12-16 13:26:36.852 [info] SSH_AUTH_SOCK not set; not forwarding SSH agent socket
2025-12-16 13:26:36.852 [info] Forwarding exec server locally via tcpForward method
2025-12-16 13:26:36.852 [info] Forwarding 127.0.0.1:39909 to 127.0.0.1:0 for container 11d586e93f542612b5141a03e60f64076ffff126844eb6ab4e45a700f2bed043
2025-12-16 13:26:36.963 [info] [tunnel-forwarding] stdout: forwarder: Forwarding (remote) 127.0.0.1:39909 to (local) 127.0.0.1:0

2025-12-16 13:26:36.967 [info] [tunnel-forwarding] stdout: forwarder: ====forwarderPort=33897====

2025-12-16 13:26:36.967 [info] Found forwarder port: 33897
2025-12-16 13:26:36.987 [info] Returning resolved authority
2025-12-16 13:26:37.091 [info] [tunnel-forwarding] stdout: forwarder: [handleClient][subprocess=3523988][spawn] options: {"port":39909,"hostname":"127.0.0.1"}

2025-12-16 13:26:37.229 [info] [tunnel-forwarding] stdout: forwarder: [handleClient][subprocess=3523988][stderr]: Connection established on 127.0.0.1:39909


2025-12-16 13:26:37.250 [info] [tunnel-forwarding] stdout: forwarder: [handleClient][subprocess=3524038][spawn] options: {"port":39909,"hostname":"127.0.0.1"}

2025-12-16 13:26:37.406 [info] [tunnel-forwarding] stdout: forwarder: [handleClient][subprocess=3524038][stderr]: Connection established on 127.0.0.1:39909


2025-12-16 13:27:00.176 [info] [tunnel-forwarding] stdout: forwarder: [handleClient][subprocess=3524897][spawn] options: {"port":39909,"hostname":"127.0.0.1"}

2025-12-16 13:27:00.368 [info] [tunnel-forwarding] stdout: forwarder: [handleClient][subprocess=3524897][stderr]: Connection established on 127.0.0.1:39909


2025-12-16 13:27:20.418 [info] [tunnel-forwarding] stdout: forwarder: [handleClient][subprocess=3525368][spawn] options: {"port":39909,"hostname":"127.0.0.1"}

2025-12-16 13:27:20.615 [info] [tunnel-forwarding] stdout: forwarder: [handleClient][subprocess=3525368][stderr]: Connection established on 127.0.0.1:39909

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like

Thanks for the detailed report and logs. The “Scanning folder for Git repositories” issue appears to be a known regression in 2.2.x that’s already been escalated to engineering - see this related topic.

Since your setup involves SSH + Dev Containers, I’m adding this report to the existing bug tracking. Could you confirm if the issue also occurs when connecting directly to the remote SSH machine (without the Docker container)?

The issue does not occur when connecting to the remote machine without attaching to a docker container

1 Like

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.