Files
canina/docs/managed-disk-maintenance.md
T
Canina Hermes 63ced7b44a
Owned disk maintenance only / maintenance (push) Successful in 11s
ops: protect mounted test artifacts and document capacity adoption gate
2026-11-19 07:33:24 +00:00

2.3 KiB

Owned disk maintenance

Installed only by .gitea/workflows/managed-disk.yml on the dedicated ops branch. This workflow never calls an application deployment. The daily system timer manages only unused >24h Docker builder cache (no --all, images, volumes or logs) and explicit marked test children under /opt/services/canina/.managed-disk/tests. Unmarked directories, Git/env/dependency-bearing trees, symlinks, mounts and open files are preserved. Tests use temporary roots, not privileged installer fixtures.

Shared heavy work entry point:

python3 -B /opt/services/canina/.managed-disk/managed-disk.py build COMMAND ARG...

Holds .managed-disk/heavy.lock for the entire subprocess and requires >=20GiB available immediately before execution. This is an installed opt-in guard, NOT a global reservation: existing application build dispatchers do not yet acquire it. Migration of each dispatcher belongs in its reviewed release CI. Do not claim shared serialization is complete until all producers adopt it. Current lower headroom intentionally rejects new guarded heavy builds.

No existing test artifacts are automatically marked. New disposable tests may create .disposable-test containing exactly canina-managed-test-v1\n; expiry is seven days. Tests must acquire the same lock when creating/using that namespace. Existing source/donor/archive paths are outside this policy.

Container log gate

Fresh inspection confirms older containers including Traefik, Nexus and databases have json-file with empty options. The daemon already has defaults; these do not retrofit existing containers. The exact per-service Compose option for the next separately authorized release is:

logging:
  driver: json-file
  options:
    max-size: "10m"
    max-file: "3"

Do not apply a broad override or recreate these services now. Traefik/DB/VPN downtime is not authorized. No live log truncation is permitted. Each affected service's managed Compose source must receive the scoped option through its own existing release path, followed by explicit downtime approval and a verified recreation. This document is a configuration recommendation, not an installed log-rotation change.

No historical backup staging, cloud history, named volume, source checkout or protected review image is retired by this maintenance.