hermes-s6-container-supervision

Diagnose and manage s6-overlay services in Hermes Docker containers.

1|Updated Jul 31, 2026
One-click install
npx skills add https://github.com/icyzh/hermes-web --skill hermes-s6-container-supervision-icyzh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hermes-s6-container-supervision
Source: https://github.com/icyzh/hermes-web/tree/main/optional-skills/devops/hermes-s6-container-supervision
Command: npx skills add https://github.com/icyzh/hermes-web --skill hermes-s6-container-supervision-icyzh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves operational friction when managing s6-overlay services within the Hermes Docker environment, specifically addressing issues with service startup, profile gateway reconciliation, and container lifecycle management.

Core Features & Use Cases

  • Service Diagnostics: Quickly inspect the status of per-profile gateways and static services using s6-svstat.
  • Lifecycle Management: Manually trigger service restarts, stops, or starts for specific profile gateways without restarting the entire container.
  • Boot Reconciliation: Troubleshoot the cont-init.d boot process to ensure persistent profile gateways are correctly restored and supervised.

Quick Start

Use the hermes-s6-container-supervision skill to inspect the status of the gateway service for the coder profile.

Frequently Asked Questions about hermes-s6-container-supervision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the status of s6 services in a Docker container?▼

The s6-container-supervision utilities run s6-svstat against s6-overlay service directories inside the Hermes Docker container to report per-profile gateway and static service status.

Why does my s6-overlay cont-init.d boot script fail to restore persistent profile gateways?▼

s6-overlay cont-init.d boot scripts fail to restore profile gateways when persistent volume structures are missing or misconfigured. Troubleshooting the cont-init.d boot process reconciles and supervises persistent profile gateways.

Can I restart a specific s6 profile gateway without restarting the entire Docker container?▼

You can manually trigger service restarts, stops, or starts for specific s6 profile gateways without restarting the Docker container. This lifecycle management requires access to internal s6-overlay binary paths.

Does s6-overlay supervision work with Hermes Docker persistent volumes?▼

s6-overlay supervision works with Hermes Docker persistent volumes to perform service reconciliation and status reporting. Access to persistent volume structures is required to manage per-profile gateway lifecycles.

What is the best way to debug per-profile gateway lifecycles in s6-overlay?▼

The best way to debug per-profile gateway lifecycles in s6-overlay is using s6-svstat to inspect service states and manually triggering starts or stops. This isolates gateway reconciliation issues without full container restarts.