hermes-s6-container-supervision

You can debug a per-profile gateway in s6-overlay by verifying run scripts and checking service states. This Skill guides you through inspecting cont-init.d and s6-rc.d to diagnose why the gateway fails to start, restart, or survive container restarts.

The Architecture B pattern is a Docker run-time model where the CMD operates as the main program under s6 supervision. It dictates correct startup sequencing and exit behavior to ensure container stability and reliable service supervision.

To add a static service to the s6-overlay supervision tree, you modify cont-init.d and s6-rc.d directories to influence boot-time behavior. This involves describing required files, implementing integration steps, and running validation checks to ensure the service loads correctly at container boot.

Your Docker container may fail to start reliably if s6-overlay boot-time wiring is incorrect. You need to verify cont-init.d and s6-rc.d configurations, ensure the Architecture B main-program pattern is followed, and run validation checks to reconcile container boot and runtime supervision.

Yes, you can use s6-service commands to troubleshoot Hermes Agent container startup issues. By starting a Hermes container and using these commands alongside cont-init.d changes, you can execute a guided debugging workflow to stabilize container startup and runtime supervision.