Fix release publish-image Docker host diagnostic regression #338

New issue

Closed

opened 2026-07-08 16:53:11 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-08 16:53:11 +00:00

Owner

CI run 707 failed in publish-image on coilyco-flight-deck/agentic-os:

https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/actions/runs/707/jobs/1/attempt/1

Relevant log excerpt:

Docker version 29.6.1, build 8900f1d
docker daemon reachable at tcp://172.19.0.1:2375
selected DOCKER_HOST=tcp://172.19.0.1:2375
Client:
 Version:           29.6.1
 ...
failed to connect to the docker API at unix:///var/run/docker.sock; check if the path is correct and if the daemon is running: dial unix /var/run/docker.sock: connect: no such file or directory

Root cause:

.forgejo/workflows/release.yml Resolve docker host tests each candidate with docker -H "$h" info.
It then writes DOCKER_HOST=$h to $GITHUB_ENV, which only affects later steps.
The same step immediately runs docker version without -H "$h" and without exporting DOCKER_HOST, so Docker falls back to unix:///var/run/docker.sock and exits 1.

Fix:

In Resolve docker host, either run the diagnostic as docker -H "$h" version, or export DOCKER_HOST="$h" before running plain docker version.
Keep writing DOCKER_HOST=$h to $GITHUB_ENV for later steps.
Check the rest of publish-image for same-step Docker commands added after host detection.
Land to main and verify the next release run gets past Resolve docker host.

Use Codex. Claude rate limit is exhausted for the week.

CI run 707 failed in `publish-image` on `coilyco-flight-deck/agentic-os`: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/actions/runs/707/jobs/1/attempt/1 Relevant log excerpt: ```text Docker version 29.6.1, build 8900f1d docker daemon reachable at tcp://172.19.0.1:2375 selected DOCKER_HOST=tcp://172.19.0.1:2375 Client: Version: 29.6.1 ... failed to connect to the docker API at unix:///var/run/docker.sock; check if the path is correct and if the daemon is running: dial unix /var/run/docker.sock: connect: no such file or directory ``` Root cause: - `.forgejo/workflows/release.yml` `Resolve docker host` tests each candidate with `docker -H "$h" info`. - It then writes `DOCKER_HOST=$h` to `$GITHUB_ENV`, which only affects later steps. - The same step immediately runs `docker version` without `-H "$h"` and without exporting `DOCKER_HOST`, so Docker falls back to `unix:///var/run/docker.sock` and exits 1. Fix: - In `Resolve docker host`, either run the diagnostic as `docker -H "$h" version`, or `export DOCKER_HOST="$h"` before running plain `docker version`. - Keep writing `DOCKER_HOST=$h` to `$GITHUB_ENV` for later steps. - Check the rest of `publish-image` for same-step Docker commands added after host detection. - Land to `main` and verify the next release run gets past `Resolve docker host`. Use Codex. Claude rate limit is exhausted for the week.

coilyco-ops added the

autonomy

headless

label

2026-07-08 16:53:18 +00:00

coilyco-ops commented

2026-07-08 16:53:22 +00:00

Author

Owner

🔒 Reserved by ward agent --harness codex — container engineer-codex-agentic-os-338 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-08T16:53:19Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force 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/agentic-os#338 · branch issue-338 · harness codex · workflow direct-main
Run: engineer-codex-agentic-os-338 · ward v0.444.0 · dispatched 2026-07-08T16:53:19Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Issue body as seeded:

CI run 707 failed in `publish-image` on `coilyco-flight-deck/agentic-os`:

https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/actions/runs/707/jobs/1/attempt/1

Relevant log excerpt:

` ` `text
Docker version 29.6.1, build 8900f1d
docker daemon reachable at tcp://172.19.0.1:2375
selected DOCKER_HOST=tcp://172.19.0.1:2375
Client:
 Version:           29.6.1
 ...
failed to connect to the docker API at unix:///var/run/docker.sock; check if the path is correct and if the daemon is running: dial unix /var/run/docker.sock: connect: no such file or directory
` ` `

Root cause:

- `.forgejo/workflows/release.yml` `Resolve docker host` tests each candidate with `docker -H "$h" info`.
- It then writes `DOCKER_HOST=$h` to `$GITHUB_ENV`, which only affects later steps.
- The same step immediately runs `docker version` without `-H "$h"` and without exporting `DOCKER_HOST`, so Docker falls back to `unix:///var/run/docker.sock` and exits 1.

Fix:

- In `Resolve docker host`, either run the diagnostic as `docker -H "$h" version`, or `export DOCKER_HOST="$h"` before running plain `docker version`.
- Keep writing `DOCKER_HOST=$h` to `$GITHUB_ENV` for later steps.
- Check the rest of `publish-image` for same-step Docker commands added after host detection.
- Land to `main` and verify the next release run gets past `Resolve docker host`.

Use Codex. Claude rate limit is exhausted for the week.

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

— Codex, via ward agent

🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-agentic-os-338` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-08T16:53:19Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` 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/agentic-os#338` · branch `issue-338` · harness `codex` · workflow `direct-main` - **Run:** `engineer-codex-agentic-os-338` · ward `v0.444.0` · dispatched `2026-07-08T16:53:19Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). **Issue body as seeded:** ``` CI run 707 failed in `publish-image` on `coilyco-flight-deck/agentic-os`: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/actions/runs/707/jobs/1/attempt/1 Relevant log excerpt: ` ` `text Docker version 29.6.1, build 8900f1d docker daemon reachable at tcp://172.19.0.1:2375 selected DOCKER_HOST=tcp://172.19.0.1:2375 Client: Version: 29.6.1 ... failed to connect to the docker API at unix:///var/run/docker.sock; check if the path is correct and if the daemon is running: dial unix /var/run/docker.sock: connect: no such file or directory ` ` ` Root cause: - `.forgejo/workflows/release.yml` `Resolve docker host` tests each candidate with `docker -H "$h" info`. - It then writes `DOCKER_HOST=$h` to `$GITHUB_ENV`, which only affects later steps. - The same step immediately runs `docker version` without `-H "$h"` and without exporting `DOCKER_HOST`, so Docker falls back to `unix:///var/run/docker.sock` and exits 1. Fix: - In `Resolve docker host`, either run the diagnostic as `docker -H "$h" version`, or `export DOCKER_HOST="$h"` before running plain `docker version`. - Keep writing `DOCKER_HOST=$h` to `$GITHUB_ENV` for later steps. - Check the rest of `publish-image` for same-step Docker commands added after host detection. - Land to `main` and verify the next release run gets past `Resolve docker host`. Use Codex. Claude rate limit is exhausted for the week. ``` Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.444.0). </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a commit

2026-07-08 16:55:45 +00:00

fix: use resolved docker host for release diagnostics

coilyco-ops closed this issue

2026-07-08 16:56:06 +00:00

coilyco-ops commented

2026-07-08 16:56:27 +00:00

Author

Owner

WARD-OUTCOME: done - fixed the release publish-image Docker host diagnostic
The change was straightforward and the validation behaved cleanly once the branch had an upstream. The only friction was the review gate being advisory-only because no second model family was available in this container, so confidence is good on the code change and slightly lower on review coverage.
PR-BODY-NOTE: ADVISORY-ONLY REVIEW: no heterogeneous reviewer family was available besides the worker (codex), so the adversarial panel could not run and did NOT gate this diff. Dropped: opencode (unavailable: opencode not on PATH); codex (worker's own family - never reviews its own diff). A human should review this change with the extra scrutiny an unrun panel would have applied.

WARD-OUTCOME: done - fixed the release publish-image Docker host diagnostic The change was straightforward and the validation behaved cleanly once the branch had an upstream. The only friction was the review gate being advisory-only because no second model family was available in this container, so confidence is good on the code change and slightly lower on review coverage. PR-BODY-NOTE: ADVISORY-ONLY REVIEW: no heterogeneous reviewer family was available besides the worker (codex), so the adversarial panel could not run and did NOT gate this diff. Dropped: opencode (unavailable: opencode not on PATH); codex (worker's own family - never reviews its own diff). A human should review this change with the extra scrutiny an unrun panel would have applied.

coilyco-ops referenced this issue

2026-08-10 02:28:21 +00:00

actions-run-one-line accepts an inlined program on one line, defeating its own stated intent #989

coilyco-ops referenced this issue

2026-08-10 02:45:36 +00:00

Reject Actions run steps that inline a program body #990