You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature request: Start/Stop buttons at the container group level #93
Please add Start and Stop buttons at the group level (e.g. a Compose project like microsoft-azure-servicebus-emulator), so all containers in a group can be started or stopped with a single click.
This is the same behavior that Docker Desktop and OrbStack already offer: both let you start/stop an entire Compose project from the group row with one click.
Problem
Currently, the play button is only shown for each container individually (and on hover for the group row it isn't clear whether it starts the whole group). When working with multi-container setups, starting or stopping them one by one is slow and tedious.
In my daily workflow, a single group can contain 10–30 containers (databases, emulators, message brokers, APIs, etc.). Toggling them individually every time I switch projects takes a lot of clicks.
Proposed solution
Show a Start button on the group row when all/some containers are stopped.
Show a Stop button on the group row when any container is running.
(Nice to have) Restart for the whole group, and the same actions in the group's context menu (...).
Ideally respect the dependency order (e.g. depends_on in Docker Compose), similar to docker compose start / docker compose stop.
Example
Group microsoft-azure-servicebus-emulator contains servicebus-emulator and sqledge. With a group-level Start button, both would start together in one click instead of starting each container separately.
Why it's useful
Much faster switching between projects/environments
Fewer clicks for large stacks (10–30 containers)
Matches how developers think about Compose stacks: as one unit
Consistent with Docker Desktop and OrbStack, making it easier for users coming from those tools
Activity
sonswift commentedon Oct 27, 2026
Thanks for the suggestion! We've noted your request and will let you know when there are updates.