hermes-s6-container-supervision

s6-overlay supervision manages Hermes Agent Docker container processes by running PID 1 to control s6-rc services, runtime-registered gateway services, and the main-program execution pattern. It handles initialization scripts and coordinates the service lifecycle during boot reconciliation.

To debug a failing s6 supervised gateway service, diagnose startup failures, restart issues, and ownership problems by inspecting the supervision state errors. Check s6-rc service registration logs and verify Hermes container boot reconciliation to identify the root cause.

The best way to add a static service to an s6-overlay supervision tree involves registering the service through s6-rc, modifying gateway run scripts, and ensuring proper Docker initialization flow. Maintain Hermes container boot reconciliation to integrate the new service cleanly.

Your Hermes container gateway keeps restarting under s6 supervision due to supervision state errors, incorrect service registration, or ownership problems in the run scripts. Inspect s6-rc logs and verify the main-program execution pattern to resolve the restart loop.

Yes, you need to understand s6-rc service registration to maintain Hermes Docker containers. Troubleshooting container supervision, reconciling profiles, and modifying gateway run scripts all require knowledge of s6-overlay service registration and boot reconciliation behavior.

You can modify Docker initialization scripts without breaking the s6 supervision tree by following proper service management procedures. Ensure changes to static services and gateway run scripts align with s6-overlay registration patterns and Hermes container boot reconciliation requirements.