Fix director cleanup fallback without local Docker socket #1290

Merged
coilyco-ops merged 1 commit from issue-1011 into main 2026-07-14 19:01:20 +00:00
Member

This fixes the director read-only surface cleanup path so a live session stops implying that /var/run/docker.sock exists when it does not yet. Fresh director surfaces still mount the socket, but already-running ones now tell the operator to restart warded for the next launch and use the brokered ward agent stop <owner/repo#N> cleanup path from the surface.

  • Updated the reap error, read-only surface doctrine, and operator docs to name the brokered fallback.
  • Added tests for the no-socket director surface case and the surfaced restart guidance.
  • Validation: ward exec build, TMPDIR=/tmp go test ./cmd/ward -run 'TestComposeContextReadOnlyBlock|TestAgentReapSweepReportsUnsupportedOnReadOnlyDirectorSurface', pre-commit run --all-files.

closes #1011
ward.workflow: pull-request-and-merge

This fixes the director read-only surface cleanup path so a live session stops implying that `/var/run/docker.sock` exists when it does not yet. Fresh director surfaces still mount the socket, but already-running ones now tell the operator to restart `warded` for the next launch and use the brokered `ward agent stop <owner/repo#N>` cleanup path from the surface. - Updated the reap error, read-only surface doctrine, and operator docs to name the brokered fallback. - Added tests for the no-socket director surface case and the surfaced restart guidance. - Validation: `ward exec build`, `TMPDIR=/tmp go test ./cmd/ward -run 'TestComposeContextReadOnlyBlock|TestAgentReapSweepReportsUnsupportedOnReadOnlyDirectorSurface'`, `pre-commit run --all-files`. closes #1011 ward.workflow: pull-request-and-merge
fix: point director cleanup at brokered stop
All checks were successful
test / test (pull_request) Successful in 3m5s
12e935ea8a
Sign in to join this conversation.
No description provided.