NEC-396: install-deployer.sh --check calls the feedback board "running an image the file does not name": STALE_IMAGES ignores Compose profiles #356
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
dependencies
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
security
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!356
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-396-install-deployersh-check-calls-the-feedb"
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?
Task: NEC-396 — https://projectron.nerchure.com/tasks/418
install-deployer.sh --check called the feedback board on accounts "running an image the file does not name" on every run: STALE_IMAGES compared running images with
docker compose config --images, which lists only the active profiles, and the board runs in profile board while .env says COMPOSE_PROFILES=identity. It now asks with --profile "*" (every profile's images) and --no-env-resolution (one missing env_file, such as board.env on a host without the board, fails the whole listing otherwise). Riding along, NEC-398: the ops box's --check counted up and declared differently (a replica or a by-name profile service failed the box), printed ok whatever the counts when an image was unnamed (2/3 up passed), and passed 0/0 when Compose could not list anything. Both counts are now per service against one list; a running service the file declares in no profile fails by name; a list Compose could not give fails as such. All checked against real Compose v5.3.1 with the installer's own snippets and throwaway local containers; every new rule mutation-checked. Nothing is installed after merge; docs/changes/NEC-396-stale-images-profiles/spec.md lists the read-only --check to run.Spec:
docs/changes/NEC-396-stale-images-profiles/spec.mdAlso fixes NEC-398: install-deployer.sh --check on the ops box counts up and declared differently: a profile service or a scaled one reads as needing attention
Changelog
NONE
A required ${X:?} that .env leaves unset fails both `config --services` listings while every container runs on, and `ps` with them or not. The ops branch read the silence as empty lists, counted 0 declared and 0 up, and passed the box as `ok` with `all hosts verified`. That predates NEC-396, but it made "every declared service up earns an ok" untrue. A list Compose could not give is now `unread=` and fails as such; a file declaring no service for its active profiles fails too; and only the "*" listing failing (one broken service in a profile left off) says so rather than calling every other profile's running service undeclared. Checked with the installer's own snippet against real Compose v5.3.1 on throwaway local containers. The fake ops host now declares and runs Caddy by default rather than answering nothing, and every earlier ops test holds against it. Three tests, each mutation-checked. Found by the second review. Task: NEC-396 Also-fixes: NEC-398 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EV8ztbNSLvgwmCT4jFUWfh