Docker Extension Is Broken in Cursor After Extension Updates

Bug Reports
1

Hello!

Problem:
Remote Development in DevContainers over SSH doesn’t work anymore. It seems like the problem is related to recent updates of Cursor extensions.

My use case:
I use macOS 15.5 to connect over SSH to a remote Ubuntu machine where I have a DevContainer. It had been working fine until today.

Problem details:
When I connected to an existing DevContainer, I faced the following problems:

  • The Docker extension tab no longer appears in Cursor. The extension itself (ms-azuretools.vscode-docker) is still installed in the DevContainer, but the tab is missing, and there are no commands for it in the command palette. I know that VSCode is switching to the new “Containers” extension (ms-azuretools.vscode-containers), but it is also not available in Cursor.
    image
    image851×538 30.3 KB
  • The Remote Explorer tab doesn’t show any DevContainers — only an infinite loading spinner.
    image
    image845×569 11.1 KB
  • The “DevContainers: Rebuild and Reopen in Container” option is no longer available in the command palette.
    image
    image861×323 35.5 KB

I had Cursor 50.7 when I first faced the issue. Then I reinstalled version 49.6, but the problem was still there. After that, I downloaded Cursor from the website, installed it again, and got version 50.5 — the problem remained. I was also unable to install Cursor 50.7 again because it says, “There are currently no updates available.”

Then, I removed my existing DevContainer manually, opened the source SSH machine, and pressed “DevContainers: Reopen in Container”. The container was rebuilt. When I connected to it, I saw the Docker extension tab, but the other problems were still there.

Extension versions:

  • ms-azuretools.vscode-docker: v1.29.4
  • anysphere.remote-containers: v1.0.3

Then I saw a suggestion to reload the window to update both extensions (I cannot attach a screenshot, because there is a limit of 3 screenshot for new users)

After reloading, the Docker tab disappeared again, and the remote extension still didn’t work. Updated versions were:

  • ms-azuretools.vscode-docker: v2.0.0
  • anysphere.remote-containers: v1.0.4

Cursor version was still 50.5. When switching back from the DevContainer to the SSH host, the problems remained.

Some conclusions:

  1. The ms-azuretools.vscode-docker extension v2.0.0 is not supported yet (at least over SSH).
  2. The anysphere.remote-containers extension doesn’t support DevContainers over SSH.
  3. The ms-azuretools.vscode-containers extension is not supported yet.
  4. The “Check for Updates” feature doesn’t work correctly.

This issue is crucial for me because a huge part of my workflow depends on interacting with Docker containers inside the IDE. I’ll try to find a way to disable auto-updates for the Docker extension to keep it available — hopefully that helps.

3 Likes
3

Have same issue, docker extension not showing on the primary bar (the docker icon).
Please fix it since i am using it so much

1 Like
5

Have the same issue I miss my docker extension.

1 Like
6

Hey all, thanks for the reports here!

Our in-house extensions expert, @ravirahman , should hopefully jump in on this when he’s next available (unfortunately now being the weekend, that could be Monday at the latest), but should help get this resolved asap!

Sorry for any inconvenience with this at the moment :pensive_face:

1 Like
8

Hi all, thanks for sharing these issues, and @am1ter , especially appreciate the detailed report.

Re: the MS docker extension: it runs on the remote host, so it would need to be installed there after establishing and SSH connection. Could you check the “extension host - remote” output panel to see if there are any logs there for the extension failing to activate? Usually, this extension would not be installed inside the devcontainer itself – only on the ssh host – unless if you are trying to do docker in docker (which we don’t support).

Re: the MS containers extension: we need to verify compatibility with Cursor before it will show up in the marketplace. Let me take a look here to see if there are any compatibility issues.

Re: the cursor docker container: this does support docker over ssh when also using the anysphere remote ssh extension. The panel on the left will show the local docker containers (if any are available), similar to how the ssh extension shows local ssh hosts even if already connected to one. It could stay stuck with “loading” if docker on your local computer is slow to respond. But, this wouldn’t affect connecting to a docker container over SSH.

Let me take a look at the rebuild and reopen in container command.

Could you elaborate why you would like to use the docker extension when already connected to the container – would be very helpful to understand the use case here, so I can test that workflow.

And also, are you running into issues where the client fails to connect to the remote containers? If so, it would be great if you could share the logs from the “Remote - SSH” and “Remote - Dev Containers” output consoles. Thanks!

9

I also ran into this issue this morning.

Usually, this extension would not be installed inside the devcontainer itself – only on the ssh host – unless if you are trying to do docker in docker (which we don’t support).

The extension has been working fine for months and even last night, and then it was gone today. Confusingly, the extensions page says “Extension is enabled on 'SSH: myself” but I can’t navigate to it to use it.

Could you elaborate why you would like to use the docker extension when already connected to the container – would be very helpful to understand the use case here, so I can test that workflow.

There’s some confusing terminology here, but the “Docker” extension is the one for just viewing containers / images / volumes in the sidebar, to make it easy to see what is up/down and attach to them. Just recently, this popular extension was refactored by MSFT into a “Container Tools” extension with a Docker configuration, since they are supporting other container runtimes like Podman. Separately, there is a set of extensions around dev containers to connect a workspace to a running container, which is what the anysphere extension also does, but that is different.

part of my workflow where I am experiencing issues
Docker extension: ms-azuretools.vscode-docker
(new version) Container tools extension: GitHub - microsoft/vscode-containers: Container Tools Extension for Visual Studio Code

similar but distinct
MSFT Dev Containers extension: ms-vscode-remote.remote-containers
Anysphere Dev Containers extension: anysphere.remote-containers

Re: the MS containers extension: we need to verify compatibility with Cursor before it will show up in the marketplace. Let me take a look here to see if there are any compatibility issues.

I did some quick searching and found a reddit discussion about MSFT recently having a license change/enforcement action regarding extensions authored by MSFT – suggesting that MSFT is starting to disable all VSCode forks (not just Cursor) from using certain extensions on the VSCode marketplace. The thread suggests some workarounds. Though if this is a TOS issue, workarounds will be a game of cat-and-mouse.

That said – the Container Tools extension license is itself MIT, if you look at the GitHub repo

1 Like
11

Hi! I was able to reproduce this issue when upgrading to version 2.0.0 of ms-azuretools.vscode-docker. Microsoft changed this into an extension pack that points to ms-azuretools.vscode-containers, which was previously not visible in Cursor.

We have fixed this and ms-azuretools.vscode-containers should now show up in the Cursor extension marketplace. If you are on version 2.0.0 of the Docker extension, please make sure to also install ms-azuretools.vscode-containers. The “Containers” tab should then be visible in the sidebar.

1 Like
12

Hi, I have encountered a problem. Can you help me?

13

doesn’t let me connect now, mentioned here Container Tools - #19 by patrickwasp

14

Thank you @ravirahman, @danperks, and everyone else who reported their problems too.

  1. After I installed ms-azuretools.vscode-containers, which is no longer hidden, the Docker extension ms-azuretools.vscode-docker v2.0.0 started working without any problems. This particular issue seems to be resolved, but users still need to know that ms-azuretools.vscode-containers must be installed.
  2. In my case, the Remote Explorer tab still doesn’t work. Here are the logs:

Remote - SSH

[18:59:22.814] Log Level: 2
[18:59:22.821] Opening exec server for ssh-remote+ssh.alekseisemenov.local
[18:59:22.824] VS Code version: 0.50.5
[18:59:22.824] Remote-SSH version: [email protected]
[18:59:22.824] darwin arm64
[18:59:22.828] Initizing new exec server for ssh-remote+ssh.alekseisemenov.local
[18:59:22.829] Acquiring local install lock: /var/folders/9y/hqmst68s6t94kmk4n1lhm7fh0000gn/T/vscode-remote-ssh-a51a2521-install.lock
[18:59:22.830] Looking for existing server data file at /Users/amiter/Library/Application Support/Cursor/User/globalStorage/ms-vscode-remote.remote-ssh/vscode-ssh-host-a51a2521-96e5b01ca25f8fbd4c4c10bc69b15f6228c80770-0.113.1-es/data.json
[18:59:22.830] Found local server running: {"remoteListeningOn":{"port":33069},"osReleaseId":"ubuntu","arch":"x86_64","sshAuthSock":"/tmp/ssh-XXXXrQ5Fxa/agent.1997068","display":"","tmpDir":"/run/user/1000","platform":"linux","execServerToken":"719bd8b2-ad8f-453d-98da-e06b48ef5296","pid":90119,"ipcHandlePath":"/var/folders/9y/hqmst68s6t94kmk4n1lhm7fh0000gn/T/vscode-ssh-askpass-4aef150d071ab74bdb89afa0ce99488f934993fd.sock","socksPort":56740,"startupTime":1748898945767}
[18:59:22.834] Found running server - short-circuiting install
[18:59:22.835] Starting forwarding server. local port 56436 -> socksPort 56740 -> remotePort 33069
[18:59:22.835] Forwarding server listening on port 56436
[18:59:22.835] Waiting for ssh tunnel to be ready
[18:59:22.836] Tunneled port 33069 to local port 56436
[18:59:22.836] Resolved "ssh-remote+ssh.alekseisemenov.local" to "port 56436"
[18:59:22.836] Resolving exec server at port 56436
[18:59:22.836] [Forwarding server port 56436] Got connection 0
[18:59:22.837] [Forwarding server port 56436] Got connection 1
[18:59:22.885] Exec server for ssh-remote+ssh.alekseisemenov.local created and cached

Extension host (Remote)

2025-06-02 21:59:24.801 [info] Extension host with pid 276532 started
2025-06-02 21:59:24.802 [info] Lock '/home/vscode/.cursor-server/data/User/workspaceStorage/f78f87f65d1567c2c148d94f5f9995c1/vscode.lock': Lock acquired.
2025-06-02 21:59:24.947 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2025-06-02 21:59:24.948 [info] ExtensionService#_doActivateExtension anysphere.cursorpyright, startup: false, activationEvent: 'onLanguage:python'
2025-06-02 21:59:24.948 [info] ExtensionService#_doActivateExtension ms-python.python, startup: false, activationEvent: 'onLanguage:python', root cause: charliermarsh.ruff
2025-06-02 21:59:24.949 [info] ExtensionService#_doActivateExtension adpyke.vscode-sql-formatter, startup: false, activationEvent: 'onLanguage:sql'
2025-06-02 21:59:25.375 [info] ExtensionService#_doActivateExtension charliermarsh.ruff, startup: false, activationEvent: 'onLanguage:python'
2025-06-02 21:59:25.375 [info] ExtensionService#_doActivateExtension ms-python.debugpy, startup: false, activationEvent: 'onLanguage:python'
2025-06-02 21:59:25.519 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
2025-06-02 21:59:25.520 [info] ExtensionService#_doActivateExtension spmeesseman.vscode-taskexplorer, startup: true, activationEvent: '*'
2025-06-02 21:59:25.611 [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
2025-06-02 21:59:25.611 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2025-06-02 21:59:25.924 [info] Eager extensions activated
2025-06-02 21:59:25.924 [info] ExtensionService#_doActivateExtension anysphere.cursor-retrieval, startup: false, activationEvent: 'onStartupFinished'
2025-06-02 21:59:25.925 [info] ExtensionService#_doActivateExtension anysphere.cursor-shadow-workspace, startup: false, activationEvent: 'onStartupFinished'
2025-06-02 21:59:25.925 [info] ExtensionService#_doActivateExtension anysphere.cursor-tokenize, startup: false, activationEvent: 'onStartupFinished'
2025-06-02 21:59:25.925 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2025-06-02 21:59:25.925 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2025-06-02 21:59:25.925 [info] ExtensionService#_doActivateExtension dbaeumer.vscode-eslint, startup: false, activationEvent: 'onStartupFinished'
2025-06-02 21:59:25.925 [info] ExtensionService#_doActivateExtension eamodio.gitlens, startup: false, activationEvent: 'onStartupFinished'
2025-06-02 21:59:26.867 [info] ExtensionService#_doActivateExtension GitHub.vscode-pull-request-github, startup: false, activationEvent: 'onStartupFinished'
2025-06-02 21:59:27.105 [info] ExtensionService#_doActivateExtension vscode.tunnel-forwarding, startup: false, activationEvent: 'onTunnel'
2025-06-02 21:59:27.706 [error] Error: connect ECONNREFUSED 0.0.0.0:443
	at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
2025-06-02 21:59:27.706 [error] Error: connect ECONNREFUSED 0.0.0.0:443
	at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
2025-06-02 21:59:29.258 [error] Error: connect ECONNREFUSED 0.0.0.0:443
	at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
2025-06-02 21:59:29.463 [error] Error: connect ECONNREFUSED 0.0.0.0:443
	at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
2025-06-02 21:59:30.231 [error] Error: connect ECONNREFUSED 0.0.0.0:443
	at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
2025-06-02 21:59:30.426 [error] Error: connect ECONNREFUSED 0.0.0.0:443
	at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
2025-06-02 21:59:30.677 [info] ExtensionService#_doActivateExtension vscode.configuration-editing, startup: false, activationEvent: 'onLanguage:jsonc'
2025-06-02 21:59:30.677 [info] ExtensionService#_doActivateExtension vscode.json-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2025-06-02 21:59:30.677 [info] ExtensionService#_doActivateExtension vscode.typescript-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2025-06-02 21:59:30.677 [info] ExtensionService#_doActivateExtension ms-azuretools.vscode-containers, startup: false, activationEvent: 'onLanguage:dockerfile'
2025-06-02 21:59:31.030 [error] Error: connect ECONNREFUSED 0.0.0.0:443
	at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
2025-06-02 21:59:32.497 [error] Error: connect ECONNREFUSED 0.0.0.0:443
	at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
2025-06-02 21:59:33.250 [error] Error: connect ECONNREFUSED 0.0.0.0:443
	at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
2025-06-02 21:59:33.251 [error] Error: connect ECONNREFUSED 0.0.0.0:443
	at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
2025-06-02 21:59:33.639 [error] Error: connect ECONNREFUSED 0.0.0.0:443
	at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
2025-06-02 21:59:35.930 [error] Error: connect ECONNREFUSED 0.0.0.0:443
	at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
2025-06-02 21:59:36.613 [error] Error: connect ECONNREFUSED 0.0.0.0:443
	at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
2025-06-02 21:59:37.308 [error] Error: connect ECONNREFUSED 0.0.0.0:443
	at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
2025-06-02 21:59:40.880 [error] Error: connect ECONNREFUSED 0.0.0.0:443
	at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
	at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)
2025-06-02 21:59:59.356 [error] Error: connect ECONNREFUSED 0.0.0.0:443
	at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
	at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)
15

Hi @am1ter, could you elaborate on what you mean by the remote explorer tab doesn’t work? Like are no remotes showing up there, or when you select one it fails to connect?

Also, from the logs, it looks like you’re using the Vscode remote ssh extension, which is quite old. We released our own replacement recently – attaching a screenshot. Could you try switching to this one?

image
image925×267 17 KB

17

Hi @ravirahman, I also had some difficulties with Remote SSH + Remote Dev Containers with Cursor 0.50.7, anysphere.remote-containers 1.0.5, anysphere.remote-ssh 1.0.4.

I ended up getting it to work by running the “Dev-Containers> Re-open in container” .
It does reload / reconnect frequently (almost exactly every 5 minutes), but that might be an issue with my host machine / network / SSH configuration.

I ran into some confusing UX differences between the local and remote versions:

When connected to the remote machine, I only see these options:

Screenshot 2025-06-03 at 09.45.18
Screenshot 2025-06-03 at 09.45.181156×720 28.4 KB

Clicking “Dev Container” installs the MS dev container extension, which is incompatible with anysphere.remote-containers.

Locally, this is what I see (clicking “Open Folder in Container” works):

Screenshot 2025-06-03 at 09.45.57
Screenshot 2025-06-03 at 09.45.571164×880 38.4 KB

19

Hi @conradt:

I ended up getting it to work by running the “Dev-Containers> Re-open in container” .
It does reload / reconnect frequently (almost exactly every 5 minutes), but that might be an issue with my host machine / network / SSH configuration.

Could you share the logs for the “Remote - SSH” and “Remote - Dev Container” output consoles?

Clicking “Dev Container” installs the MS dev container extension, which is incompatible with anysphere.remote-containers .

Locally, this is what I see (clicking “Open Folder in Container” works):

From your last screenshot, it looks like you have both the Anysphere and VSCode dev containers installed. Could you uninstall the VSCode one (since you have the Anysphere Remote SSH extension installed?) The extension recommendation may show the VSCode one while we transition to our own replacement.

20

@ravirahman Yeah, ms-vscode.remote-explorer was installed and used by default. I haven’t seen any suggestion to install Anyphere’s version of it. I’ve just installed anysphere.remote-ssh. It works, but I still see the loader in the “DEV CONTAINERS” section of the “Remote Extension” tab (and I’m not sure that it should have been fixed by using another extension). The rest seems good.

image
image756×392 10.6 KB

@ravirahman Also, I’ve just noticed that I forgot to answer your question here:

Could you elaborate why you would like to use the docker extension when already connected to the container – would be very helpful to understand the use case here, so I can test that workflow.

I develop in a DevContainer. It means my IDE is installed in a container, but my application has many different parts, and all of them run in Docker containers on the same remote host where the DevContainer is located. This means that to manage Docker containers, I have to use the CLI or the IDE’s Docker extension. For example, streaming logs from a Docker container to the IDE is very useful.

22

@conradt @ravirahman I have the same issue with anysphere.remote-ssh v. 1.0.4. I don’t have such problem with ms-vscode.remote-explorer.

Here is some logs after a reconnect:

Remote - Dev Containers:

[Error  - 21:27:53.912] Forwarder process errored on exit, disposing of local tunnel: Error: [command][d04467eb-4ed6-42eb-9359-5e6da0798072] Socket closed without exit code
[Info  - 21:27:53.912] Stopping forwarder process
[Info  - 21:27:53.968] [ssh_auth_socket][/tmp/cursor-remote-ssh-f13d9cb5-b96c-4282-9941-42f809e9f610.sock] SSH host stream ended
[Error  - 21:27:53.968] [ssh_auth_socket][/tmp/cursor-remote-ssh-f13d9cb5-b96c-4282-9941-42f809e9f610.sock] forwarder process done ended with error: Error: [command][29d8d768-1670-4db4-a102-33d8db1fbbcf] Socket closed without exit code
[Info  - 21:27:53.968] [ssh_auth_socket][/tmp/cursor-remote-ssh-f13d9cb5-b96c-4282-9941-42f809e9f610.sock] forwarder process stdout ended
[Info  - 21:27:54.967] Resolving dev container authority 'dev-container+7b2273657474696e6754797065223a22636f6e666967222c22776f726b737061636550617468223a222f686f6d652f616d697465722f636f64696e672f63616c6c71222c22646576636f6e7461696e657250617468223a222f686f6d652f616d697465722f636f64696e672f63616c6c712f2e646576636f6e7461696e65722f646576636f6e7461696e65722e6a736f6e227d' (attempt #15) container '{"settingType":"config","workspacePath":"..."}'
[Info  - 21:27:54.967] Using exec server from resolve options
[Info  - 21:27:54.967] Deleting remote devcontainer cli at /tmp/devcontainer-cli-346934c1-d429-423a-959c-cd6e998aeec6
[Info  - 21:27:54.967] Starting Dev Containers dev-container+7b2273657474696e6754797065223a22636f6e666967222c22776f726b737061636550617468223a222f686f6d652f616d697465722f636f64696e672f63616c6c71222c22646576636f6e7461696e657250617468223a222f686f6d652f616d697465722f636f64696e672f63616c6c712f2e646576636f6e7461696e65722f646576636f6e7461696e65722e6a736f6e227d
[Info  - 21:27:54.980] Remote devcontainer cli deleted

Remote - SSH:

[Info  - 21:26:52.874] [remote-ssh] Pinging remote server on port 54679
[Info  - 21:26:52.875] [command][0d1a7d6c-92eb-43f0-8bca-39513d427b8b] Sending command request: {"command":"echo","args":["1"],"env":{"SSH_AUTH_SOCK":"/tmp/ssh-XXXXZRi9Lz/agent.2924665"},"token":"56ccc8a8-3996-41e7-b3a2-bd789962345a","id":"0d1a7d6c-92eb-43f0-8bca-39513d427b8b"}
[Info  - 21:26:52.876] [forwarding][multiplex][127.0.0.1:54679 -> 127.0.0.1:37289][9953a64b-655a-4360-bc6a-c527c0ba9897] received connection request
[Trace  - 21:26:52.878] (ssh_tunnel) stderr: debug1: Connection to port 61727 forwarding to socks port 0 requested.

[Trace  - 21:26:52.878] (ssh_tunnel) stderr: debug1: channel 9: new dynamic-tcpip [dynamic-tcpip] (inactive timeout: 0)

[Info  - 21:26:52.882] [forwarding][multiplex][127.0.0.1:54679 -> 127.0.0.1:61727 -> 127.0.0.1:37289][9953a64b-655a-4360-bc6a-c527c0ba9897] socks forwarding established
[Info  - 21:26:52.893] [command][0d1a7d6c-92eb-43f0-8bca-39513d427b8b] Process exited with code 0
[Info  - 21:26:52.893] [forwarding][multiplex][127.0.0.1:54679 -> 127.0.0.1:61727 -> 127.0.0.1:37289][9953a64b-655a-4360-bc6a-c527c0ba9897] socks connection closed
[Info  - 21:26:52.893] [command][0d1a7d6c-92eb-43f0-8bca-39513d427b8b] Socket close event received
[Trace  - 21:26:52.898] (ssh_tunnel) stderr: debug1: channel 9: free: direct-tcpip: listening port 61727 for 127.0.0.1 port 37289, connect from 127.0.0.1 port 63184 to 127.0.0.1 port 61727, nchannels 10

[Info  - 21:27:52.894] [remote-ssh] Pinging remote server on port 54679
[Info  - 21:27:52.895] [forwarding][multiplex][127.0.0.1:54679 -> 127.0.0.1:37289][763d36dc-7390-4136-bae2-8162d06e0869] received connection request
[Info  - 21:27:52.896] [command][3f3000c8-bddf-44ad-a742-d65c6e96995a] Sending command request: {"command":"echo","args":["1"],"env":{"SSH_AUTH_SOCK":"/tmp/ssh-XXXXZRi9Lz/agent.2924665"},"token":"56ccc8a8-3996-41e7-b3a2-bd789962345a","id":"3f3000c8-bddf-44ad-a742-d65c6e96995a"}
[Trace  - 21:27:52.896] (ssh_tunnel) stderr: debug1: Connection to port 61727 forwarding to socks port 0 requested.
debug1: channel 9: new dynamic-tcpip [dynamic-tcpip] (inactive timeout: 0)

[Info  - 21:27:52.901] [forwarding][multiplex][127.0.0.1:54679 -> 127.0.0.1:61727 -> 127.0.0.1:37289][763d36dc-7390-4136-bae2-8162d06e0869] socks forwarding established
[Info  - 21:27:52.908] [command][3f3000c8-bddf-44ad-a742-d65c6e96995a] Process exited with code 0
[Info  - 21:27:52.908] [forwarding][multiplex][127.0.0.1:54679 -> 127.0.0.1:61727 -> 127.0.0.1:37289][763d36dc-7390-4136-bae2-8162d06e0869] socks connection closed
[Info  - 21:27:52.908] [command][3f3000c8-bddf-44ad-a742-d65c6e96995a] Socket close event received
[Trace  - 21:27:52.913] (ssh_tunnel) stderr: debug1: channel 9: free: direct-tcpip: listening port 61727 for 127.0.0.1 port 37289, connect from 127.0.0.1 port 63524 to 127.0.0.1 port 61727, nchannels 10

[Trace  - 21:27:53.441] (ssh_tunnel) stderr: debug1: client_input_channel_req: channel 2 rtype exit-status reply 0
debug1: client_input_channel_req: channel 2 rtype [email protected] reply 0

[Trace  - 21:27:53.441] (ssh_tunnel) stderr: debug1: channel 2: free: client-session, nchannels 9

[Trace  - 21:27:53.442] (ssh_tunnel) stdout: Code server is exiting as the process 2924724 died

[Info  - 21:27:53.908] [tunnel-forwarding][127.0.0.1:61796 -> 127.0.0.1:61727 -> 127.0.0.1:42191][974aca43-f1f3-47cb-95db-f10cae7f23c8] socks connection closed
[Info  - 21:27:53.908] [forwarding][multiplex][127.0.0.1:54679 -> 127.0.0.1:61727 -> 127.0.0.1:37289][7b2c7620-663a-4d4c-ad32-44858e63a843] socks connection closed
[Info  - 21:27:53.911] [command][d04467eb-4ed6-42eb-9359-5e6da0798072] Socket end event received
[Info  - 21:27:53.912] [command][d04467eb-4ed6-42eb-9359-5e6da0798072] Socket close event received
[Info  - 21:27:53.912] [tunnel] disposing of tunnel (remote) 127.0.0.1:42191 -> (local) 127.0.0.1:61796
[Info  - 21:27:53.912] [command][d04467eb-4ed6-42eb-9359-5e6da0798072] Stdin end
[Info  - 21:27:53.913] [tunnel-forwarding][127.0.0.1:61796 -> 127.0.0.1:61727 -> 127.0.0.1:42191][276b570d-4daa-43a2-923a-ad48a26e5e49] socks connection closed
[Info  - 21:27:53.913] [tunnel-forwarding][127.0.0.1:61796 -> 127.0.0.1:61727 -> 127.0.0.1:42191][974aca43-f1f3-47cb-95db-f10cae7f23c8] local connection closed
[Info  - 21:27:53.915] [tunnel-forwarding][127.0.0.1:61796 -> 127.0.0.1:42191] server closed
[Info  - 21:27:53.915] [tunnel-forwarding][127.0.0.1:61796 -> 127.0.0.1:61727 -> 127.0.0.1:42191][276b570d-4daa-43a2-923a-ad48a26e5e49] local connection closed
[Trace  - 21:27:53.917] (ssh_tunnel) stderr: debug1: channel 4: free: direct-tcpip: listening port 61727 for 127.0.0.1 port 42191, connect from 127.0.0.1 port 61813 to 127.0.0.1 port 61727, nchannels 8

[Trace  - 21:27:53.917] (ssh_tunnel) stderr: debug1: channel 7: free: direct-tcpip: listening port 61727 for 127.0.0.1 port 37289, connect from 127.0.0.1 port 61795 to 127.0.0.1 port 61727, nchannels 7

[Trace  - 21:27:53.919] (ssh_tunnel) stderr: debug1: channel 8: free: direct-tcpip: listening port 61727 for 127.0.0.1 port 42191, connect from 127.0.0.1 port 61798 to 127.0.0.1 port 61727, nchannels 6

[Info  - 21:27:53.925] [remote-ssh][resolveExecServer] Resolving connection
[Info  - 21:27:53.925] Resolving ssh remote authority 'ssh.alekseisemenov.local' (Unparsed 'ssh-remote+ssh.alekseisemenov.local') (attempt #15)
[Info  - 21:27:53.935] Terminating existing SSH process with pid: 57037
[Info  - 21:27:53.967] Using configured platform linux for remote host ssh.alekseisemenov.local
[Trace  - 21:27:53.967] hostname: ssh.alekseisemenov.local, remote server install map: {}
[Info  - 21:27:53.967] Using askpass script: /Users/amiter/.cursor/extensions/anysphere.remote-ssh-1.0.4/dist/scripts/launchSSHAskpass.sh with javascript file /Users/amiter/.cursor/extensions/anysphere.remote-ssh-1.0.4/dist/scripts/sshAskClient.js. Askpass handle: /var/folders/9y/hqmst68s6t94kmk4n1lhm7fh0000gn/T/cursor-ssh-k4Amze/socket.sock
[Trace  - 21:27:53.968] (ssh_tunnel): exit: code=null signal=SIGKILL
[Info  - 21:27:53.968] [forwarding][multiplex][127.0.0.1:54679 -> 127.0.0.1:61727 -> 127.0.0.1:37289][3930e191-107f-4649-831c-7659b0bf4df5] socks connection closed
[Info  - 21:27:53.968] [forwarding][multiplex][127.0.0.1:54679 -> 127.0.0.1:61727 -> 127.0.0.1:37289][5f8e0f9c-4aa1-4c07-a962-36b276e4ef9f] socks connection closed
[Info  - 21:27:53.968] [command][75bed789-228b-4021-86b8-b17889e04fb5] Socket end event received
[Info  - 21:27:53.968] [command][29d8d768-1670-4db4-a102-33d8db1fbbcf] Socket end event received
[Info  - 21:27:53.968] [command][29d8d768-1670-4db4-a102-33d8db1fbbcf] Socket close event received
[Info  - 21:27:53.968] [command][75bed789-228b-4021-86b8-b17889e04fb5] Stdin end
[Info  - 21:27:53.968] [command][75bed789-228b-4021-86b8-b17889e04fb5] Stdin end
[Info  - 21:27:53.968] [command][75bed789-228b-4021-86b8-b17889e04fb5] Socket close event received
[Info  - 21:27:53.968] [command][29d8d768-1670-4db4-a102-33d8db1fbbcf] Stdin end
[Trace  - 21:27:53.969] Launching SSH server with command: ssh -v -T -D 63531 ssh.alekseisemenov.local bash --login -c 'echo
24

Could you share the logs for the “Remote - SSH” and “Remote - Dev Container” output consoles?

Here are the output logs:

Dev Container Logs 
[Info  - 21:27:08.329] [ssh_auth_socket][/tmp/cursor-remote-ssh-34668068-7ded-476a-84a4-818227dd2da0.sock] forwarder process stdout ended
[Info  - 21:27:08.356] [ssh_auth_socket][/tmp/cursor-remote-ssh-34668068-7ded-476a-84a4-818227dd2da0.sock] SSH host stream ended
[Error  - 21:27:08.356] [ssh_auth_socket][/tmp/cursor-remote-ssh-34668068-7ded-476a-84a4-818227dd2da0.sock] forwarder process done ended with error: Error: [command][ddf71c16-746b-4343-aab6-6c4d07d36f1c] Socket closed without exit code
[Error  - 21:27:08.358] Forwarder process errored on exit, disposing of local tunnel: Error: [command][0df4ca1c-d158-4862-86ab-18bb1b60b8c9] Socket closed without exit code
[Info  - 21:27:08.359] Stopping forwarder process
SSH Logs 
[Info  - 21:26:04.669] [forwarding][multiplex][127.0.0.1:52216 -> 127.0.0.1:52179 -> 127.0.0.1:44855][8894194b-c3e1-4dc1-99de-3bf64de291e9] socks forwarding established
[Info  - 21:26:04.755] [command][a807e62a-fa67-4d50-82fe-c59491b0b5bb] Process exited with code 0
[Info  - 21:26:04.755] [forwarding][multiplex][127.0.0.1:52216 -> 127.0.0.1:52179 -> 127.0.0.1:44855][8894194b-c3e1-4dc1-99de-3bf64de291e9] socks connection closed
[Info  - 21:26:04.755] [command][a807e62a-fa67-4d50-82fe-c59491b0b5bb] Socket close event received
[Trace  - 21:26:04.856] (ssh_tunnel) stderr: debug1: channel 2: free: direct-tcpip: listening port 52179 for 127.0.0.1 port 44855, connect from 127.0.0.1 port 52668 to 127.0.0.1 port 52179, nchannels 9

[Info  - 21:27:04.759] [remote-ssh] Pinging remote server on port 52216
[Info  - 21:27:04.760] [command][49d64c5a-5881-4fee-9362-dfe112697838] Sending command request: {"command":"echo","args":["1"],"env":{"SSH_AUTH_SOCK":"/tmp/ssh-8vW0ZAERnq/agent.1758483"},"token":"602982e8-fd70-47cf-8b7f-44c1805525ad","id":"49d64c5a-5881-4fee-9362-dfe112697838"}
[Info  - 21:27:04.760] [forwarding][multiplex][127.0.0.1:52216 -> 127.0.0.1:44855][67b47bff-5620-4063-8e1f-7a8ecf66deae] received connection request
[Trace  - 21:27:04.760] (ssh_tunnel) stderr: debug1: Connection to port 52179 forwarding to socks port 0 requested.
debug1: channel 2: new dynamic-tcpip [dynamic-tcpip] (inactive timeout: 0)

[Info  - 21:27:04.839] [forwarding][multiplex][127.0.0.1:52216 -> 127.0.0.1:52179 -> 127.0.0.1:44855][67b47bff-5620-4063-8e1f-7a8ecf66deae] socks forwarding established
[Info  - 21:27:04.920] [command][49d64c5a-5881-4fee-9362-dfe112697838] Process exited with code 0
[Info  - 21:27:04.920] [forwarding][multiplex][127.0.0.1:52216 -> 127.0.0.1:52179 -> 127.0.0.1:44855][67b47bff-5620-4063-8e1f-7a8ecf66deae] socks connection closed
[Info  - 21:27:04.920] [command][49d64c5a-5881-4fee-9362-dfe112697838] Socket close event received
[Trace  - 21:27:04.997] (ssh_tunnel) stderr: debug1: channel 2: free: direct-tcpip: listening port 52179 for 127.0.0.1 port 44855, connect from 127.0.0.1 port 52732 to 127.0.0.1 port 52179, nchannels 9

[Info  - 21:27:08.328] [forwarding][multiplex][127.0.0.1:52216 -> 127.0.0.1:52179 -> 127.0.0.1:44855][161332f9-7ab8-400d-aaed-dec420ccddd4] socks connection closed
[Info  - 21:27:08.329] [command][26911e3e-18b0-4783-9acb-4b92c55868dd] Socket end event received
[Info  - 21:27:08.329] [command][26911e3e-18b0-4783-9acb-4b92c55868dd] Socket close event received
[Info  - 21:27:08.329] [command][ddf71c16-746b-4343-aab6-6c4d07d36f1c] Stdin end
[Info  - 21:27:08.354] [forwarding][multiplex][127.0.0.1:52216 -> 127.0.0.1:52179 -> 127.0.0.1:44855][fce73e0f-bec5-427f-947f-ff28d21bf1c1] socks connection closed
[Info  - 21:27:08.355] [command][ddf71c16-746b-4343-aab6-6c4d07d36f1c] Socket end event received
[Trace  - 21:27:08.355] (ssh_tunnel) stderr: debug1: channel 4: FORCE input drain

[Info  - 21:27:08.356] [command][ddf71c16-746b-4343-aab6-6c4d07d36f1c] Socket close event received
[Info  - 21:27:08.356] [command][26911e3e-18b0-4783-9acb-4b92c55868dd] Stdin end
[Info  - 21:27:08.356] [command][26911e3e-18b0-4783-9acb-4b92c55868dd] Stdin end
[Info  - 21:27:08.358] [forwarding][multiplex][127.0.0.1:52216 -> 127.0.0.1:52179 -> 127.0.0.1:44855][83df3a37-b31b-44e2-a921-1166dfc37997] socks connection closed
[Info  - 21:27:08.358] [command][0df4ca1c-d158-4862-86ab-18bb1b60b8c9] Socket end event received
[Info  - 21:27:08.358] [command][0df4ca1c-d158-4862-86ab-18bb1b60b8c9] Socket close event received
[Info  - 21:27:08.358] [tunnel] disposing of tunnel (remote) 127.0.0.1:38363 -> (local) 127.0.0.1:52319
[Info  - 21:27:08.359] [command][0df4ca1c-d158-4862-86ab-18bb1b60b8c9] Stdin end
[Info  - 21:27:08.362] [tunnel-forwarding][127.0.0.1:52319 -> 127.0.0.1:52179 -> 127.0.0.1:38363][ab6cc3b2-7f0b-41ce-9327-8b155d53677d] socks connection closed
[Info  - 21:27:08.362] [tunnel-forwarding][127.0.0.1:52319 -> 127.0.0.1:52179 -> 127.0.0.1:38363][503dc9da-2b46-4074-a193-cd9ebf5c7963] socks connection closed
[Info  - 21:27:08.362] [tunnel-forwarding][127.0.0.1:52319 -> 127.0.0.1:52179 -> 127.0.0.1:38363][503dc9da-2b46-4074-a193-cd9ebf5c7963] local connection closed
[Info  - 21:27:08.362] [tunnel-forwarding][127.0.0.1:52319 -> 127.0.0.1:38363] server closed
[Info  - 21:27:08.363] [tunnel-forwarding][127.0.0.1:52319 -> 127.0.0.1:52179 -> 127.0.0.1:38363][ab6cc3b2-7f0b-41ce-9327-8b155d53677d] local connection closed
[Info  - 21:27:08.368] [remote-ssh][resolveExecServer] Resolving connection
[Info  - 21:27:08.368] Resolving ssh remote authority '███' (Unparsed 'ssh-remote+7b22686f73744e616d65223a226e79227d') (attempt #2)
[Info  - 21:27:08.382] Terminating existing SSH process with pid: 59390
[Trace  - 21:27:08.413] hostname: ███, remote platform map: {"███":"linux"}
[Info  - 21:27:08.413] Using configured platform linux for remote host ███
[Trace  - 21:27:08.413] hostname: ███, remote server install map: {}
[Trace  - 21:27:08.413] (ssh_tunnel) stderr: debug1: channel 5: free: direct-tcpip: listening port 52179 for 127.0.0.1 port 44855, connect from 127.0.0.1 port 52316 to 127.0.0.1 port 52179, nchannels 8

From your last screenshot, it looks like you have both the Anysphere and VSCode dev containers installed. Could you uninstall the VSCode one (since you have the Anysphere Remote SSH extension installed?) The extension recommendation may show the VSCode one while we transition to our own replacement.

I do not have the MS Dev Container or MS Remote SSH extensions installed, locally or on the remote.
The problem is that clicking the “Dev Container” installs the MS Dev Container extension.

26

Hi @am1ter and @conradt:

I still see the loader in the “DEV CONTAINERS” section of the “Remote Extension” tab

This is fixed in version 1.0.6 of the Anysphere remote containers plugin. This happened when docker was not installed (or failed to run) locally, but otherwise should not have affected the extension. The latest version displays an error message here instead.

@am1ter: In your logs, I see:

[Trace - 21:27:53.442] (ssh_tunnel) stdout: Code server is exiting as the process 2924724 died

If you didn’t explicitly kill this process, it’s possible that the OS terminated it if it was under resource pressure (e.g. out of CPU / memory). Could you try running an htop on your remote system and see if the CPU or memory is pegged?

@conradt – In your logs, I see:

[Trace - 21:27:08.355] (ssh_tunnel) stderr: debug1: channel 4: FORCE input drain

Do you have any flags set in your SSH config file (e.g. SSH agent forwarding? X11 forwarding?) It looks like some of the sockets are closing around when that log line was emitted, which suggests that the SSH client might be trying to terminate the connection, causing the reloads. If you have these flags set, could you try commenting them out?