chore(rs2000): normalize legacy compose ownership for logopts exceptions #796

New issue

Closed

opened 2026-06-17 21:27:04 +02:00 by codex · 0 comments

codex commented

2026-06-17 21:27:04 +02:00

Collaborator

Summary

After the RS2000 Docker log rotation rollout, current-compose services with complete runtime inputs were recreated and now report 64m/3. The remaining exceptions are legacy compose, builder internals, or manual/static containers and should not be force-recreated.

Scope

Map each remaining exception to one of:

current compose service to recreate safely;
legacy desired-state import;
retirement/sunset;
explicit manual/static exception;
builder-internal exception governed by BuildKit GC.

Spec sources (whitelist)

runbooks/rs2000-disk-hygiene.md
state/reports/rs2000-backup-logopts-followup-2026-06-17.md
state/reports/rs2000-runtime-health-closeout-2026-06-17.md

Do NOT read

Secret values or runtime env contents.
Full repo before the three whitelist sources prove a missing source-controlled dependency.
Runtime service private data; Docker inspect metadata is enough for ownership mapping.

Extracted context

Remaining closeout exceptions:

buildx_buildkit_default
buildx_buildkit_kan-ductor-builder0
home-platform-element-web-1
home-platform-gmail-openclaw-broker-1
home-platform-mirotalk-admin-1
home-platform-mirotalk-sfu-1
home-platform-np-1
home-platform-np-meerkat-frontend-1
home-platform-np-memos-1
home-platform-np-openhabittracker-1
home-platform-np-radicale-1
home-platform-np-silverbullet-1
home-platform-np-tududi-1
home-platform-synapse-1
home-platform-vault-1
iskra-ics-static

Acceptance criteria

Report maps every container above to a target class.
No service is recreated from compose that renders missing env warnings.
Current-compose services that can be safely recreated are handled one at a time with smoke evidence.
Legacy services get follow-up import/retire issues instead of ad-hoc runtime mutation.
End state is either 64m/3 or a documented intentional exception.

Hard stops

No docker compose --remove-orphans.
No manual docker rm / volume deletion.
No Vault unseal/bootstrap.
No auth/routing changes while normalizing ownership.

Source

Created from RS2000 runtime health closeout on 2026-06-17.

## Summary After the RS2000 Docker log rotation rollout, current-compose services with complete runtime inputs were recreated and now report `64m/3`. The remaining exceptions are legacy compose, builder internals, or manual/static containers and should not be force-recreated. ## Scope Map each remaining exception to one of: - current compose service to recreate safely; - legacy desired-state import; - retirement/sunset; - explicit manual/static exception; - builder-internal exception governed by BuildKit GC. ## Spec sources (whitelist) - `runbooks/rs2000-disk-hygiene.md` - `state/reports/rs2000-backup-logopts-followup-2026-06-17.md` - `state/reports/rs2000-runtime-health-closeout-2026-06-17.md` ## Do NOT read - Secret values or runtime env contents. - Full repo before the three whitelist sources prove a missing source-controlled dependency. - Runtime service private data; Docker inspect metadata is enough for ownership mapping. ## Extracted context Remaining closeout exceptions: ```text buildx_buildkit_default buildx_buildkit_kan-ductor-builder0 home-platform-element-web-1 home-platform-gmail-openclaw-broker-1 home-platform-mirotalk-admin-1 home-platform-mirotalk-sfu-1 home-platform-np-1 home-platform-np-meerkat-frontend-1 home-platform-np-memos-1 home-platform-np-openhabittracker-1 home-platform-np-radicale-1 home-platform-np-silverbullet-1 home-platform-np-tududi-1 home-platform-synapse-1 home-platform-vault-1 iskra-ics-static ``` ## Acceptance criteria - Report maps every container above to a target class. - No service is recreated from compose that renders missing env warnings. - Current-compose services that can be safely recreated are handled one at a time with smoke evidence. - Legacy services get follow-up import/retire issues instead of ad-hoc runtime mutation. - End state is either `64m/3` or a documented intentional exception. ## Hard stops - No `docker compose --remove-orphans`. - No manual `docker rm` / volume deletion. - No Vault unseal/bootstrap. - No auth/routing changes while normalizing ownership. ## Source Created from RS2000 runtime health closeout on 2026-06-17.

codex added the

labels

2026-06-17 21:27:04 +02:00