Background,
You can now add Cursor as a managed application to individual projects.
This enables Workbench to automatically connect Cursor to the project container.
See here for the latest release information.
However, the implementation uses a local container runtime to establish the connection.
If you DON”T have Docker or Podman running locally, the connection will fail.
A future release will fix this issue.
Affected Users: Remote Only Desktop App installs.
This only affects users with the Desktop App in “remote only” mode.
Resolution: Full Local Install or Manually Connect Cursor
The instructions assume that you already added Cursor to a project. See how here.
Option One: Do the full local install
This will install and start the container runtime. See how in our user guide here.
Note: If you are in the situation where you have a local container runtime but the Desktop App is in remote only mode, you can just start the local runtime before launching Cursor in the project. See this topic in our user guide. Without proper group membership, Workbench can’t access the container runtime
Option Two: Start a project container and connect Cursor to it manually
Step One: Open the project in Workbench and start the container
-
Select Location Manager > Location Card > Location Window > Project Card
-
Select Project Tab > Dashboard > Project Container > Start Container
Step Two: Connect a Cursor window to the location and to the project container
-
Open a new Cursor window > Select Connect via SSH
-
Select the location name or IP from the options provided in the top search bar
-
Wait for the connection to be made
-
Then go to Search Bar (Top) > Dev Containers: Attach to a Running Container
-
Hit Enter and Select Drop Down > Select the container name > Hit Enter
Step Three: Open the project repository in the Cursor Window
-
Select Cursor window > Open Folder (LHS)
-
Locate the project folder and select it