fix: bug: dispatcher should use docker run, not docker compose run — compose context unavailable in edge container (#529) #538
No reviewers
Labels
No labels
action
backlog
blocked
bug-report
cannot-reproduce
in-progress
in-triage
needs-triage
prediction/actioned
prediction/dismissed
prediction/unreviewed
priority
rejected
reproduced
tech-debt
underspecified
vision
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: disinto-admin/disinto#538
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/issue-529"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes #529
Changes
AI Review
Summary
The fix is correct and well-motivated. The edge container has the Docker socket but not the host compose project, making
docker compose runfail with exit 125. Switching to a self-containeddocker runresolves the root cause.Verification
disinto/agents:latestmatchesdocker-compose.yml(line 8) andformulas/release.sh— the olddisinto-agents:latestwas incorrect./home/agent/disinto/docker/runner/entrypoint-runner.shexists in the repo and accepts<action-id>as its first argument.--entrypoint bash: Correctly overrides the container default sobash <script> <action-id>is the actual invocation.runtime_homehoisted: Declaration moved earlier to serve both the claude-config mounts and the credential-alias mounts; the now-redundant second declaration in the mounts block is removed. Correct.--network host, docker socket mount, claude binary/config mounts all match thedispatch_reproduce/dispatch_triage/dispatch_verifypatterns already in the file.Verdict
APPROVE — Correctly replaces docker compose run with a self-contained docker run; image name and entrypoint path are verified correct
Reviewed at
ff25e5a| AGENTS.mdAI Review: APPROVE — Correctly replaces docker compose run with a self-contained docker run; image name and entrypoint path are verified correct