Force composer to run commands in a specific shell/Docker container?

Discussions
1

Hi,

I need to run commands in specific Docker containers for my project. I can’t use dev containers since I have multiple containers per project and it would be a pain to

What I’ve tried:

  1. Specifying the shell using “@Containers: …”
  2. Providing the Docker container ID directly
  3. Requesting commands to always use “docker exec”

Current Behavior:

  • Commands appear to run but without visible output
  • Commands always hang and require manual cancellation
  • Even when it works once, subsequent commands revert to using the workspace shell
  • This creates a frustrating cycle of running → hanging → canceling → repeat

Has anyone found a reliable way to make Cursor/Composer consistently use a specific pre-opened shell or at least a specific Docker container?

2

Just wanted to point out that this has been fixed as of 0.48, It nows use the same command as the terminal you @.

In my case it will prepend all commands with the correct docker exec command.

1 Like
3

Great, you can mark your last post as the solution :slight_smile:

4

It lasted a day, back to not being able to use commands it just hangs forever, wonder if it has to do with the fact I’m using remote ssh.

5

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