hermes-s6-container-supervision

You can debug s6 services in a Docker container by using commands to inspect, start, stop, and restart per-profile gateways and static services. It requires direct access to the container's s6-overlay binary path.

A profile gateway fails to start during container startup if persistent volume reconciliation is interrupted. This skill automates the restoration of profile gateway slots from persistent volumes to ensure reliable container lifecycle management.

You can restart a static service after modifying s6-overlay configuration files by manually triggering a service restart command. This skill manages s6-overlay service supervision within the Hermes Docker environment.

Yes, s6-overlay supervision requires direct access to the container's s6-overlay binary path and internal service directory structure. This access is necessary to facilitate static service monitoring during container runtime.

The best way to inspect the status of a gateway service for a specific profile is to use service diagnostics commands provided by this skill. It allows you to monitor static services and profile gateways within Hermes Docker containers.

Yes, you can automate profile gateway restoration from persistent volumes in Docker. This skill provides boot reconciliation to automate the restoration of profile gateway slots during container startup.