fix: remove supervisor from agents container cron — cannot run without Docker access #231

New issue

Closed

opened 2026-04-05 16:11:28 +00:00 by dev-bot · 0 comments

dev-bot commented

2026-04-05 16:11:28 +00:00

Collaborator

Problem

The supervisor agent (supervisor-run.sh + preflight.sh) requires host-level access:

Docker CLI to check container health (docker ps, docker stats)
Docker socket for container operations
Host-level pgrep for stale process detection

The agents container does not have Docker installed or the socket mounted. Running the supervisor inside the container fails at preflight.

Additionally, supervisor-run.sh has the same LOG_FILE bug as the gardener (#210) — hardcodes to $SCRIPT_DIR which is read-only in the container.

Proposed solution

Remove supervisor from the agents container entrypoint cron setup (entrypoint.sh install_project_crons should skip supervisor)
Remove .supervisor-active from state/ if present (prevent accidental container execution)
Add a comment in the cron template explaining supervisor runs on host, not in container

The supervisor will be redesigned to run on the host level — see the vision issue for that.

Affected files

docker/agents/entrypoint.sh (skip supervisor in cron setup)
state/ (remove .supervisor-active if present)

Acceptance criteria

Supervisor cron is not installed inside the agents container
No .supervisor-active file in state/
Comment in entrypoint.sh explains supervisor runs on host

## Problem The supervisor agent (supervisor-run.sh + preflight.sh) requires host-level access: - Docker CLI to check container health (docker ps, docker stats) - Docker socket for container operations - Host-level pgrep for stale process detection The agents container does not have Docker installed or the socket mounted. Running the supervisor inside the container fails at preflight. Additionally, supervisor-run.sh has the same LOG_FILE bug as the gardener (#210) — hardcodes to $SCRIPT_DIR which is read-only in the container. ## Proposed solution 1. Remove supervisor from the agents container entrypoint cron setup (entrypoint.sh install_project_crons should skip supervisor) 2. Remove .supervisor-active from state/ if present (prevent accidental container execution) 3. Add a comment in the cron template explaining supervisor runs on host, not in container The supervisor will be redesigned to run on the host level — see the vision issue for that. ## Affected files - docker/agents/entrypoint.sh (skip supervisor in cron setup) - state/ (remove .supervisor-active if present) ## Acceptance criteria - [ ] Supervisor cron is not installed inside the agents container - [ ] No .supervisor-active file in state/ - [ ] Comment in entrypoint.sh explains supervisor runs on host