hermes-s6-container-supervision

Manage s6-overlay supervision trees in Hermes Agent Docker containers.

2|Updated May 10, 2026
One-click install
npx skills add https://github.com/freedomw1987/tree_monstor --skill hermes-s6-container-supervision-freedomw1987
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hermes-s6-container-supervision
Source: https://github.com/freedomw1987/tree_monstor/tree/main/skills/software-development/hermes-s6-container-supervision
Command: npx skills add https://github.com/freedomw1987/tree_monstor --skill hermes-s6-container-supervision-freedomw1987

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the frustration of broken Hermes Agent Docker container services caused by misconfigured s6-overlay supervision trees, non-starting profile gateways, and broken container boot flows that prevent services from surviving restarts or executing correctly.

Core Features & Use Cases

  • Static Service Management: Add, remove, or modify supervised static services (like the Hermes dashboard) that run on every container start.
  • Gateway Troubleshooting: Diagnose and fix per-profile gateway issues including failure to start, crash loops, and failure to survive docker restart commands.
  • Boot Flow Customization: Modify cont-init.d boot scripts, adjust the main-wrapper.sh CMD routing logic, and understand the Architecture B pattern that uses the container CMD as the main program for correct exit code handling.
  • Use Case: For example, if a Hermes Docker container's coder profile gateway keeps crashing after every restart, use this Skill to inspect the s6 service status, fix the gateway's configuration, and ensure it stays running across container reboots.

Quick Start

Use the hermes-s6-container-supervision skill to diagnose why a Hermes Docker profile gateway is not starting after a container restart and implement the fix for the underlying configuration issue.

Frequently Asked Questions about hermes-s6-container-supervision

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

FAQPage Schema
Why does my Hermes Docker profile gateway crash or fail to start after a container restart?

Profile gateway startup failures in Hermes Docker containers stem from misconfigured s6-overlay supervision trees. Inspecting the s6 service status and correcting the per-profile gateway run command resolves crash loops and ensures uptime across reboots.

How do I add or remove supervised static services in a Docker container using s6-overlay?

To add or remove supervised static services in Docker using s6-overlay, modify the s6-overlay supervision tree configuration. This ensures services like the Hermes dashboard run reliably on every container start and survive restarts correctly.

How do I modify cont-init.d boot scripts to customize the container boot flow in Hermes Agent?

To customize the Hermes Agent container boot flow, modify the cont-init.d boot scripts and adjust the main-wrapper.sh CMD routing logic. This ensures static services initialize correctly during the container startup sequence.

Does Hermes Docker support the Architecture B CMD-as-main-program pattern for correct exit code propagation?

Yes, Hermes Docker uses the Architecture B CMD-as-main-program pattern. This design routes the container CMD through the main-wrapper.sh script, ensuring correct container exit code propagation when supervised services terminate.

What is the best way to debug a broken s6-overlay supervision tree in a Hermes Docker container?

The best way to debug a broken s6-overlay supervision tree is to inspect the s6 service status for static services and profile gateways. Fixing the per-profile gateway configuration and cont-init.d scripts restores service reliability.