From 4093b50476586fcaefa639e6191681805dfca508 Mon Sep 17 00:00:00 2001 From: sam Date: Fri, 21 Aug 2026 06:50:39 +0000 Subject: [PATCH] =?UTF-8?q?docs:=20rename=20follow-ups=20=E2=80=94=20dirty?= =?UTF-8?q?-checkout=20pull=20guidance,=20second-agent=20upgrade=20path?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 75003b2..8cd0dec 100644 --- a/README.md +++ b/README.md @@ -56,6 +56,11 @@ docker compose pull docker compose up -d ``` +(Second agent on this box? Its `compose.agent2.yml` is not auto-discovered — +upgrade it explicitly: `docker compose --env-file .env-agent2 -f +compose.agent2.yml pull && docker compose --env-file .env-agent2 -f +compose.agent2.yml up -d`.) + The agent re-authenticates and resumes polling. ## Options @@ -81,7 +86,7 @@ The agent re-authenticates and resumes polling. | Symptom | Meaning | |---|---| | `no configuration file provided: not found` | You're not in the kit directory (`compose.yml` is auto-discovered only from the directory you run in). `cd` into the `onlyscans-agent-kit` clone, or use plain `docker logs onlyscans-agent` (the container itself is fine) | -| Upgraded from an older kit (`docker-compose.agent.yml`)? | The compose file was renamed to `compose.yml` — `git pull` removes the old one. Use plain `docker compose up -d` / `logs -f` from now on; your `.env` is untouched | +| Upgraded from an older kit (`docker-compose.agent.yml`)? | The compose file was renamed to `compose.yml` — `git pull` removes the old one. Use plain `docker compose up -d` / `logs -f` from now on; your `.env` is untouched. If you EDITED the old tracked file (e.g. applied the host-network swap) `git pull` will refuse — restore it first (`git checkout -- docker-compose.agent.yml`), pull, then re-apply your change in an untracked `compose.override.yml` (auto-merged with `compose.yml`, so future pulls stay clean) | | Container exits ~1 s after start | Bad `AGENT_IDENTITY` or `AGENT_PASSWORD` — fatal by design; fix `.env` and recreate | | Agent shows **offline** centrally (`/agents`) | Container down, or no egress to `scan-api.noctools.nz:443` — check `docker logs onlyscans-agent` | | Scans stay queued | Agent online but for a different location, or targets unreachable from the container's network — try the host-network variant |