docs(wiki): trainer as a compose profile — one running service is expected, first-run pull/login, why the collector TAG bump mattered, park-2 needs no bump until a pin

Claude-Session: https://claude.ai/code/session_01FWncR69HgGPuei1dLrW3cU
2026-09-07 11:30:28 +02:00
parent 3f16925fe0
commit 3e77a4ad7c
3 changed files with 29 additions and 1 deletions
@@ -160,7 +160,9 @@ Same repo, branch and pinned `TAG` promotion, its own secret references, and —
 names its compose files — nothing booth-side lands on that host and nothing of it on a booth.
 The same stack carries the phase-B **trainer** as a compose *profile* (`train`,
 [[bodytype-classifier-training]]): a deploy never starts it; the owner runs it by hand on the host
-with `docker compose … --profile train run --rm trainer …`. Its two env lines (`TRAINER_OUT`, the
+with `docker compose … --profile train run --rm trainer …`. So after a deploy of that stack
+`docker ps` shows one container — expected; and a deploy pulls nothing for the profile, the
+first `run` does (host Docker must be logged in to the registry). Its two env lines (`TRAINER_OUT`, the
 `TRAINER_PUBLISH_TOKEN` secret reference) stay commented in `resources.toml` until the first
 publish.