Keep the Compose director visually grouped with its broker in Docker Desktop #1564

New issue

Closed

opened 2026-07-25 23:29:47 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-25 23:29:47 +00:00

Member

Problem

On Windows Docker Desktop, Ward's persistent director stack renders as a Compose application containing only the broker. The live director appears as a separate top-level container even though it belongs to the same Compose project.

The director carries the expected metadata:

com.docker.compose.project points at ward-coilyco-flight-deck-codex
com.docker.compose.service is director
com.docker.compose.oneoff is True
the director and broker share the generated Compose file and project network

A live check confirmed that the director can reach the broker and the broker accepts its commands. This is a visual ownership problem, not a broker-connectivity failure.

Likely seam

Ward launches the director with docker compose run using rm, no-deps, and an explicit container name. Compose classifies that container as a one-off, and Docker Desktop renders it outside the application group.

Test the smallest seam first by removing the explicit custom name. If Docker Desktop still separates the one-off container, assess launching the director as a regular Compose service with compose up plus attach while preserving its interactive terminal, disposable cleanup, and broker-independent lifetime.

Acceptance

Docker Desktop on Windows renders the live director under the same Compose application as its broker.
The director remains interactive and carries the expected project and service labels.
Director exit still removes only the director and leaves the broker supervised.
A director can still reach and command the broker across the shared project network.
Automated coverage protects the chosen Compose lifecycle contract, with a bounded manual Docker Desktop verification where UI behavior cannot be asserted in tests.

Defer this visual issue behind #1563, which currently blocks brokered engineer creation after the broker accepts a request.
Follow-up to the persistent broker work in #1562.

## Problem On Windows Docker Desktop, Ward's persistent director stack renders as a Compose application containing only the broker. The live director appears as a separate top-level container even though it belongs to the same Compose project. The director carries the expected metadata: * com.docker.compose.project points at ward-coilyco-flight-deck-codex * com.docker.compose.service is director * com.docker.compose.oneoff is True * the director and broker share the generated Compose file and project network A live check confirmed that the director can reach the broker and the broker accepts its commands. This is a visual ownership problem, not a broker-connectivity failure. ## Likely seam Ward launches the director with docker compose run using rm, no-deps, and an explicit container name. Compose classifies that container as a one-off, and Docker Desktop renders it outside the application group. Test the smallest seam first by removing the explicit custom name. If Docker Desktop still separates the one-off container, assess launching the director as a regular Compose service with compose up plus attach while preserving its interactive terminal, disposable cleanup, and broker-independent lifetime. ## Acceptance * Docker Desktop on Windows renders the live director under the same Compose application as its broker. * The director remains interactive and carries the expected project and service labels. * Director exit still removes only the director and leaves the broker supervised. * A director can still reach and command the broker across the shared project network. * Automated coverage protects the chosen Compose lifecycle contract, with a bounded manual Docker Desktop verification where UI behavior cannot be asserted in tests. ## Priority and related work * Defer this visual issue behind #1563, which currently blocks brokered engineer creation after the broker accepts a request. * Follow-up to the persistent broker work in #1562.

coilyco-ops referenced this issue from a commit

2026-07-26 02:32:18 +00:00

fix(agent): group director with Compose broker

coilyco-ops closed this issue

2026-07-26 02:42:49 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/ward#1564

No description provided.

Rows
Columns