Why isn’t Container Tools available in the extension marketplace
Ever since the last update, the Docker extension keeps disappearing. The only way to get it back is to uninstall and reinstall
1 Like
Same here, I have to reinstall Docker extension every time. I’m using the cursor-bin AUR package on Arch. Here are some logs that might be relevant:
2025-05-30 07:42:44.415 [error] Unable to resolve nonexistent file 'vscode-userdata:/home/theor/.config/Cursor/User/globalStorage/ms-azuretools.vscode-docker': Error: Unable to resolve nonexistent file 'vscode-userdata:/home/theor/.config/Cursor/User/globalStorage/ms-azuretools.vscode-docker'
at s6s.resolve (vscode-file://vscode-app/tmp/.mount_cursorFptVZt/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6635:62362)
at async CAo (vscode-file://vscode-app/tmp/.mount_cursorFptVZt/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:479:212696) Unable to resolve nonexistent file 'vscode-userdata:/home/theor/.config/Cursor/User/globalStorage/ms-azuretools.vscode-docker'
1 Like
As far as I can tell, the Container Tools license doesn’t prevent it from being used outside VS Code (unlike the licenses that caused issues with the Pylance, C++, and C# extensions). Also, the required engines should support Cursor’s VS Code OSS version 1.96.2: vscode-containers/package.json at 675285f130567005a245cf919fdb9c7c33fc6788 · microsoft/vscode-containers · GitHub.
Hi all, we need to check compatibility for the new MS Containers extension before it will be visible in the marketplace. It is OSS so there shouldn’t be an issue there, but there might be some API incompatibilities that we first need to check.
It is quite strange, though, that the Docker extension gets uninstalled after you install it.
@Kyrunner – what platform are you running?
@theostargazer I We don’t officially support running the client on Arch, so would recommend reaching out to the maintainers of that cursor-bin package.
It doesn’t technically gets uninstalled, but it disappears from the activity bar and from the context menu, effectively rendering it non-existent. Removing the extension and installing it again fixes the problem. Not sure what triggers it, initially I thought it’s on every editor restart, but that’s not the case. I might try running the official app image to see if the issue is reproduced there.
1 Like
I run Ubuntu server and Debian server
It doesn’t get uninstalled it disappears
1 Like
Could you share a screenshot of where it is disappearing from?
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 already 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. New installs / upgrades should automatically get both extensions.
3 Likes
Hi @patrickwasp – thanks for bringing this up. We just released version 1.0.5 of the Anysphere Remote Containers extension, which should fix this issue.
1.0.5 indeed helped; However, I’m recently facing the problem of connecting to the container:
Updating to newest version 10.0.7 doesn’t help 
Hi @maxw1489, could you share the logs from the latest version of the extension? They’re slightly more verbose which will help trace down the error. Thanks!
@ravirahman sure:
2025-06-23 09:13:25.905 [info] No remote exec server found for authority: dev-container+7b2273657474696e6754797065223a22636f6e7461696e6572222c22636f6e7461696e65724964223a22373265323438633739386337227d@ssh-remote+7b22686f73744e616d65223a224d61782d44455850524f227d; using local
2025-06-23 09:13:26.003 [info] Resolving dev container authority ‘dev-container+7b2273657474696e6754797065223a22636f6e7461696e6572222c22636f6e7461696e65724964223a22373265323438633739386337227d’ (attempt #1) container ‘{“settingType”:“container”,“containerId”:“72e248c798c7”}’
2025-06-23 09:13:26.003 [info] Using exec server from resolve options. execServerRemoteAuthority: ssh-remote+7b22686f73744e616d65223a224d61782d44455850524f227d
2025-06-23 09:13:26.003 [info] Starting Dev Containers dev-container+7b2273657474696e6754797065223a22636f6e7461696e6572222c22636f6e7461696e65724964223a22373265323438633739386337227d
2025-06-23 09:13:26.060 [info] Copying devcontainer CLI from /Users/maxwelikow/.cursor/extensions/anysphere.remote-containers-1.0.8/dist/@devcontainers to /tmp/devcontainer-cli-05d93bd2-5b65-48bc-b05c-65cf10f1321c
2025-06-23 09:13:26.089 [info] docker version: Client: Docker Engine - Community
Version: 24.0.4
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.11.1
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.32.4
Path: /usr/libexec/docker/cli-plugins/docker-compose
Server:
Containers: 8
Running: 5
Paused: 0
Stopped: 3
Images: 19
Server Version: 24.0.4
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 logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 nvidia runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 3dce8eb055cbb6872793272b4f20ed16117344f8
runc version: v1.1.7-0-g860f061
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.8.0-59-generic
Operating System: Ubuntu 22.04.2 LTS
OSType: linux
Architecture: x86_64
CPUs: 20
Total Memory: 62.63GiB
Name: Maxki2
ID: f033750f-6a53-4692-852e-3baa50d657c0
Docker Root Dir: /var/lib/docker
Debug Mode: false
Username: fabiantedexpro
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
2025-06-23 09:13:26.089 [info] Inspecting docker container 72e248c798c7
2025-06-23 09:13:26.148 [error] Error resolving dev container authority Unexpected end of JSON input
2025-06-23 09:13:28.694 [info] Devcontainer CLI written to /tmp/devcontainer-cli-05d93bd2-5b65-48bc-b05c-65cf10f1321c
2025-06-23 09:13:28.764 [info] Copying forwarder.js to /tmp/devcontainer-cli-05d93bd2-5b65-48bc-b05c-65cf10f1321c
2025-06-23 09:13:28.915 [info] Copying forwarderk8s.js to /tmp/devcontainer-cli-05d93bd2-5b65-48bc-b05c-65cf10f1321c
2025-06-23 09:13:33.404 [info] Reloading window
2025-06-23 09:13:34.309 [info] No remote exec server found for authority: dev-container+7b2273657474696e6754797065223a22636f6e7461696e6572222c22636f6e7461696e65724964223a22373265323438633739386337227d@ssh-remote+7b22686f73744e616d65223a224d61782d44455850524f227d; using local
2025-06-23 09:13:34.408 [info] Resolving dev container authority ‘dev-container+7b2273657474696e6754797065223a22636f6e7461696e6572222c22636f6e7461696e65724964223a22373265323438633739386337227d’ (attempt #1) container ‘{“settingType”:“container”,“containerId”:“72e248c798c7”}’
2025-06-23 09:13:34.408 [info] Using exec server from resolve options. execServerRemoteAuthority: ssh-remote+7b22686f73744e616d65223a224d61782d44455850524f227d
2025-06-23 09:13:34.408 [info] Starting Dev Containers dev-container+7b2273657474696e6754797065223a22636f6e7461696e6572222c22636f6e7461696e65724964223a22373265323438633739386337227d
2025-06-23 09:13:34.465 [info] Copying devcontainer CLI from /Users/maxwelikow/.cursor/extensions/anysphere.remote-containers-1.0.8/dist/@devcontainers to /tmp/devcontainer-cli-ccd11acb-cd04-484a-b5dc-6ab8985f27c1
2025-06-23 09:13:34.492 [info] docker version: Client: Docker Engine - Community
Version: 24.0.4
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.11.1
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.32.4
Path: /usr/libexec/docker/cli-plugins/docker-compose
Server:
Containers: 8
Running: 5
Paused: 0
Stopped: 3
Images: 19
Server Version: 24.0.4
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 logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 nvidia runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 3dce8eb055cbb6872793272b4f20ed16117344f8
runc version: v1.1.7-0-g860f061
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.8.0-59-generic
Operating System: Ubuntu 22.04.2 LTS
OSType: linux
Architecture: x86_64
CPUs: 20
Total Memory: 62.63GiB
Name: Maxki2
ID: f033750f-6a53-4692-852e-3baa50d657c0
Docker Root Dir: /var/lib/docker
Debug Mode: false
Username: fabiantedexpro
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
2025-06-23 09:13:34.492 [info] Inspecting docker container 72e248c798c7
2025-06-23 09:13:34.555 [error] Error resolving dev container authority Unexpected end of JSON input
2025-06-23 09:13:37.020 [info] Devcontainer CLI written to /tmp/devcontainer-cli-ccd11acb-cd04-484a-b5dc-6ab8985f27c1
2025-06-23 09:13:37.088 [info] Copying forwarder.js to /tmp/devcontainer-cli-ccd11acb-cd04-484a-b5dc-6ab8985f27c1
2025-06-23 09:13:37.223 [info] Copying forwarderk8s.js to /tmp/devcontainer-cli-ccd11acb-cd04-484a-b5dc-6ab8985f27c1
Hi @maxw1489,
Thanks for sharing these logs. From the logs, it looks like you might be on an old version of the SSH extension.
To use Docker over SSH, could you install the latest version of the Anysphere Remote SSH extension? Attaching a screenshot:
If you have the VSCode extension installed, you’ll be prompted to remove it when switching to the Anysphere SSH extension.
1 Like
Thank you for looking into! It works now 
1 Like