Can't attach Cursor to Docker Container

Bug Reports
33

@ravirahman

Thank you for your reply.

I checked my “Dev Container” version, and it was already “1.0.7”.

And I also set the docker path to the actual path value, but the issue was not resolved.

image
image1920×1032 128 KB

35

After applying the latest versions of the Anysphere extensions Dev Containers (1.0.8) and WSL (1.0.4) my issue has been resolved. Thankyou.

1 Like
37

Could you double check that docker info runs in a terminal, without sudo? We require that docker be accessible from the current user.

38

Having the same issue here..
Even if I applied the latest versions of the Anysphere extensions Dev Containers (1.0.8) and WSL (1.0.4)

Here is my error message.

Failed to install Cursor server: Failed to check Docker version – is docker installed and running?: [docker info] Command failed with exit code 1: spawn docker ENOENT: stdout:

image
image1920×1121 121 KB

image
image3134×1298 368 KB

image
image3030×1146 333 KB

40

commenting to follow this thread. similar problem here:

42

@ravirahman

Yes, it works.

I updated Dev Container extension to 1.0.8 and retried ReOpen Folder. But it didn’t work well.

image
image1920×1032 140 KB

image
image1920×1047 173 KB

44

Same Problem! I try to open a Docker container on my remote server, but the cursor cannot execute “docker info”. I can run “docker info” without root permission.

image
image960×654 52.9 KB

image
image2882×716 301 KB

46

thank you for replying
here is the settings aboutpath to docker
Shall I install docker locally? VSC doesn’t require it.

image
image1254×237 8.53 KB

Also, here is the error window. Would you please tell me how can I connect to the remote container?
image
image418×147 7.47 KB

48

I’m having the same issue. I upgraded to 1.2 and installed the requested extensions. Since then I have not been able to attach to the dev container I’ve been using.

50

This worked for me:

“”"

Solution 1: Launch Cursor from Terminal (Recommended)

The most reliable fix is to launch Cursor from your terminal where Docker is working:

If Cursor is already open, try these steps:

  1. Close Cursor completely

  2. Open Terminal and navigate to your project:

Run

cd /path/to/project

cursor .

Try the dev container again: Command Palette → “Remote-Containers: Reopen in Container”

“”"

I’m not sure why this worked, but it did.

1 Like
52

This workaround implies that docker is not on the default path. When launching Cursor from a folder via the terminal, I believe it will inherit the environment variables (including the path) from that process.

53

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