hermes-s6-container-supervision

Modify and debug the s6-overlay supervision tree in the Hermes Agent Docker image.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows users to modify, debug, or extend the s6-overlay supervision tree inside the Hermes Agent Docker image, adding new services, debugging profile gateways, and understanding the Architecture B main-program pattern.

Core Features & Use Cases

  • Service Management: Add or remove static services in the Hermes Docker image.
  • Gateway Debugging: Diagnose issues with per-profile gateways.
  • Understanding Architecture: Gain insight into the container's CMD and how leading-dash args reach the user's program.
  • Boot Scripts: Modify cont-init.d boot scripts for UID remap, volume seeding, and profile reconciliation.
  • Run-script Changes: Modify the rendered run-script for per-profile gateways.
  • Use Case: If you're working on a custom Hermes Docker image and need to troubleshoot a service that's not starting or understand how the main program is executed.

Quick Start

Use the hermes-s6-container-supervision skill to inspect a profile gateway service in a running container.

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 debug a service that is not starting in an s6-overlay Docker container?

You can debug s6-overlay services by inspecting the rendered run-script for per-profile gateways within the Docker container. This approach helps identify why a specific service is failing to start properly during the supervision tree initialization process.

What is the main-program execution pattern in the Hermes Docker image?

The main-program execution pattern in the Hermes Docker image defines how the container's CMD operates and how leading-dash arguments are passed to reach the user's program. This pattern is central to the Architecture B design within the s6-overlay supervision tree.

How do I add or remove static services in an s6-overlay supervision tree?

To add or remove static services in the s6-overlay supervision tree, you modify the service management scripts within the Docker image. This allows you to extend the Hermes Agent container with new background processes or remove unnecessary ones from the supervision tree.

Can I modify boot scripts for UID remap and volume seeding in a Docker container?

Yes, you can modify `cont-init.d` boot scripts to handle UID remap, volume seeding, and profile reconciliation in your Docker container. These scripts run during the s6-overlay initialization phase to configure the environment before services start.

Do I need prior knowledge of Docker and s6-overlay to debug profile gateways?

Yes, debugging profile gateways and modifying the supervision tree requires prior knowledge of Docker and s6-overlay. Understanding these technologies is necessary to diagnose issues with per-profile gateways and interpret the container's execution pattern effectively.

Why are my per-profile gateways failing to initialize in the Hermes Agent Docker image?

Per-profile gateways may fail to initialize due to errors in the rendered run-script or issues within the `cont-init.d` boot scripts. You should diagnose the profile reconciliation logic and inspect the run-script changes to resolve the gateway startup failure.