Would it possible to include Dockers Interface in the cloud agents interface

Ideas Feature Requests
1

image
image253×266 14.6 KB

In the editor window, you have the following screenshot (as above)

In cloud agents window, I would like to see the containers appear in the top right of the right sidebar. But I can’t seem to find it. Would it possible to make this as a feature request?

Just sharing my thoughts.

4

Hey, thanks for the feature request.

Right now, the Docker panel you see in the screenshot comes from the VS Code Docker extension, and it only works in the main editor window. The Cloud Agents window is a separate, lighter UI, and VS Code extensions, including Docker, don’t load there yet, so there isn’t a containers panel.

I’ve logged this as a feature request for parity with container management in Cloud Agents. I can’t share a timeline or make any promises, but it’s recorded, and the more votes the thread gets, the more likely it is to be reviewed.

If your main goal is to work with Docker inside the cloud agent, not just see the UI, that’s already possible via environment.json and Dockerfile-based environment setup: Cloud Environment Setup | Cursor Docs. Let me know if you’re interested in that setup and I’ll share more details.

5

Thanks for the response Dean.

Intially it’s just for the UI access request cause I don’t like to have switch between cloud agents and code editor screen when I want its docker UI to be readily accessible in the cloud agents just like you have web browser, gitlens, terminals tabs are available to use while I’m navigating between repo/workspaces threads. It helps to reduce the context switch a bit when reaching for local developer feedback loop.

I’ll. checkout the cloud env you just. shared with me as well. Looks useful. Cheers.

6

Hi @deanrie

I could use your help with docker setup inside the cloud agent. Can you pass the setup details so I can upload Dockerfile into cloud agents to start up? Thanks!

7

Hey, no problem. The Dockerfile setup is done in .cursor/environment.json in the repo root. The basic structure is:

{
  "build": {
    "dockerfile": "Dockerfile",
    "context": ".."
  },
  "install": "bash .cursor/install.sh",
  "start": "bash .cursor/start.sh",
  "terminals": []
}
  • build.dockerfile is the path to your Dockerfile relative to .cursor/
  • build.context is the build context, usually .. which is the repo root
  • install is the command to install dependencies
  • start is the command to start services
  • terminals is optional, preset terminals that show up in the Cloud Agents window

After you commit .cursor/environment.json and the Dockerfile, the agent will pick up the config and build the environment. Full docs: Cloud Environment Setup | Cursor Docs

If you plan to run Docker inside the agent docker-in-docker, add fuse-overlayfs and iptables-legacy in the Dockerfile, and make sure the cloud agent user has permission to run Docker. That’s covered in the Running Docker section at the same link.

A couple threads with working examples and common gotchas:

Let me know if anything isn’t getting picked up. Share your environment.json and the build log and we can take a look.

8

Awesome. This is very good overview. I"m hoping this same setup can apply for docker-compose yamls as well. Just have to explore the setup and see how far it takes.

9

Hey, yeah, docker-compose works in the same setup. A few things that’ll save time:

  1. In the Dockerfile, install Docker CE plus the Docker Compose plugin. For docker-in-docker, also add fuse-overlayfs and iptables-legacy.
  2. In the start command in environment.json, start the daemon with sudo service docker start. Bring up your compose services with docker compose up in start or via terminals, but don’t put docker compose up in the install or update script. That’s explicitly not recommended.
  3. Pass through the required env vars and secrets like DB creds and API keys so the containers start correctly.

Docs section Running Docker with a recommended Dockerfile: Cloud Environment Setup | Cursor Docs

Another useful thread about the compose setup: Cloud agents with docker-compose

If the daemon won’t start in the agent environment, check the Docker daemon config at /etc/docker/daemon.json. For docker-in-docker you sometimes need to disable the default bridge or iptables. If anything still isn’t picked up, send your environment.json, Dockerfile (or compose yaml), and the build log and we can take a look together.

10

Thanks. This looks good. I’ll check it out.