docker container name conflicts can crash the broker #1282

New issue

Closed

opened 2026-07-14 15:21:41 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-07-14 15:21:41 +00:00

Owner

example

docker: Error response from daemon: Conflict. The container name "/engineer-codex-agentic-os-432" is already in use by container "9cc1002e9fbb572f19fa9a1b37150926b408f3f6b3aac5a4eca6e189e959e51c". You have to remove (or rename) that container to be able to reuse that name.

example > docker: Error response from daemon: Conflict. The container name "/engineer-codex-agentic-os-432" is already in use by container "9cc1002e9fbb572f19fa9a1b37150926b408f3f6b3aac5a4eca6e189e959e51c". You have to remove (or rename) that container to be able to reuse that name.

coilysiren referenced this issue

2026-07-14 15:27:09 +00:00

director should emit colorized, space buffered, visually distinct messages about the categories of actions its performing on startup #1283

coilyco-ops commented

2026-07-15 03:36:59 +00:00

Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-ward-1282 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-15T03:36:58Z). Concurrent ward agent runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). --override-reservation overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#1282 · branch issue-1282 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1282 · ward v0.696.0 · dispatched 2026-07-15T03:36:45Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.696.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-ward-1282` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T03:36:58Z). Concurrent `ward agent` runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). `--override-reservation` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#1282` · branch `issue-1282` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1282` · ward `v0.696.0` · dispatched `2026-07-15T03:36:45Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.696.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a commit

2026-07-15 03:42:35 +00:00

Fix broker launch conflict cleanup

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-15 03:43:22 +00:00

Fix broker cleanup on Docker name conflicts #1306

coilyco-ops closed this issue

2026-07-15 03:44:51 +00:00

coilyco-ops commented

2026-07-15 03:45:30 +00:00

Member

WARDED_WORKFLOW: #1306

details

workflow: pull-request-and-merge; review summary: review gate skipped by the temporary ward default pending brokered QA
retrospective: the fix stayed local to the broker failure path and did not sprawl.
confidence: high.
surprises: none beyond the need to leave the live container alone on duplicate-name errors.
follow-ups: none.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1306 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate skipped by the temporary ward default pending brokered QA retrospective: the fix stayed local to the broker failure path and did not sprawl. confidence: high. surprises: none beyond the need to leave the live container alone on duplicate-name errors. follow-ups: none. </details>