hermes-s6-container-supervision

Debug s6-overlay container supervision by inspecting cont-init boot scripts and s6-rc service definitions to identify startup failures. You can trace static service registration, check run-script generation, and verify Docker exit-code behavior to locate the failing component in the Hermes Agent image.

Per-profile gateway persistence fails when cont-init reconciliation scripts do not properly restore gateway service slots from persistent profile state. You need to ensure boot-time scripts correctly remap ownership and seed files so the s6-rc service manager can recover the gateway lifecycle.

The container entrypoint uses an Architecture B pattern where the container CMD is the main program and user arguments flow through the wrapper correctly. This ensures the s6-overlay supervision layer routes commands properly while maintaining service lifecycle management.

Add a new static service to s6-rc by creating service definitions and generating the corresponding service manager run-scripts. You must ensure the cont-init scripts handle boot-time reconciliation and that Docker exit-code behavior remains consistent for the supervised service.

Yes, you can use s6-overlay to manage dashboard startup behavior by adjusting static s6-rc services. The supervision layer allows you to add, remove, or modify static service definitions so the dashboard starts reliably within the container lifecycle.

Modifying s6-rc service definitions requires correct handling of cont-init scripts and Docker exit-code behavior, and errors can disrupt gateway recovery across container boots. You must preserve boot-time reconciliation and per-profile gateway lifecycle state to avoid service supervision failures.