hermes-s6-container-supervision

Inspect and manage s6-overlay services within the Hermes Docker container.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/cxnaive/hermes-agent-llbot --skill hermes-s6-container-supervision-cxnaive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hermes-s6-container-supervision
Source: https://github.com/cxnaive/hermes-agent-llbot/tree/main/optional-skills/devops/hermes-s6-container-supervision
Command: npx skills add https://github.com/cxnaive/hermes-agent-llbot --skill hermes-s6-container-supervision-cxnaive

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill provides the necessary operational context to debug, modify, and manage s6-overlay services within the Hermes Docker environment, ensuring stable container orchestration.

Core Features & Use Cases

  • Service Management: Inspect, start, stop, and restart per-profile gateway services using s6-svstat and s6-svc.
  • Boot Reconciliation: Understand and troubleshoot the cont-init.d boot process, including UID/GID remapping and profile reconciliation.
  • Use Case: If a per-profile gateway fails to start after a container restart, use this skill to identify the crash loop cause and manually trigger the service recovery.

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 inspect s6-overlay service states in a Docker container?

You can inspect s6-overlay service states in a Docker container by using s6-svstat to check per-profile gateway services and s6-svc to start, stop, or restart them via the Hermes CLI service manager.

Why does a per-profile gateway fail to start after a container restart?

A per-profile gateway fails to start after a container restart due to cont-init.d boot process issues like UID/GID remapping errors or profile reconciliation failures, which you can troubleshoot and manually recover.

Do I need direct access to the s6-overlay binary path to debug Hermes services?

Yes, you need direct access to the s6-overlay binary path and the Hermes CLI service manager to perform administrative container tasks and debug service supervision effectively within the environment.

What is the cont-init.d boot process used for in Hermes Docker containers?

The cont-init.d boot process in Hermes Docker containers handles initialization tasks including UID/GID remapping and profile reconciliation to ensure per-profile gateway services start correctly during container orchestration.

How do I manually trigger service recovery for a crashed s6-overlay service?

You manually trigger service recovery for a crashed s6-overlay service by inspecting the cont-init.d boot process to identify the crash loop cause, then using s6-svc to restart the affected per-profile gateway.

Can I manage multiple profile gateway services simultaneously with s6-overlay?

You can manage multiple per-profile gateway services simultaneously using s6-svstat and s6-svc commands to inspect, start, stop, and restart individual services within the Hermes Docker container environment.