hermes-s6-container-supervision

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit is designed to help developers modify, debug, or extend the s6-overlay supervision tree inside the Hermes Agent Docker image, adding new services, understanding the architecture, and troubleshooting issues.

Core Features & Use Cases

  • Service Modification: Add or remove static services in the Docker image.
  • Gateway Debugging: Diagnose issues with per-profile gateways.
  • Understanding Architecture: Gain insights into the main-program pattern of the Architecture B.
  • Boot Script Management: Modify cont-init.d scripts for UID remapping, volume seeding, and profile reconciliation.
  • Run-script Customization: Change the run-script for per-profile gateways.
  • Use Case: When you need to extend the Hermes Agent Docker image with new services or debug why a gateway isn't functioning correctly.

Quick Start

Use the hermes-s6-container-supervision skill to add a new static service to the Hermes Docker image.

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 add a new static service to a Docker image using s6-overlay?▼

To add a static service to a Docker image using s6-overlay, you modify the supervision tree within the Hermes Agent Docker image. This involves extending the s6-overlay configuration to register and manage the new service process correctly.

Why is my per-profile gateway not functioning correctly in the Hermes Agent Docker container?▼

A per-profile gateway not functioning correctly in the Hermes Agent Docker container is diagnosed by debugging the s6-overlay supervision tree. You can modify the specific run-script for the per-profile gateway to identify and resolve the startup or execution issue.

How do I modify boot scripts in a Docker image for UID remapping and volume seeding?▼

You modify boot scripts in a Docker image for UID remapping and volume seeding by editing the `cont-init.d` scripts. These scripts are part of the s6-overlay architecture and handle profile reconciliation during the container initialization phase.

Do I need prior knowledge of s6-overlay to customize the Hermes Agent Docker image?▼

Yes, you need prior knowledge of s6-overlay and the Hermes Agent to customize the Docker image. The customization process requires understanding the main-program pattern of Architecture B to successfully modify and extend the supervision tree.

What is the best way to understand the architecture of the Hermes Agent supervision tree?▼

The best way to understand the Hermes Agent supervision tree architecture is by analyzing the s6-overlay implementation. This reveals the main-program pattern of Architecture B, showing how services are managed and how per-profile gateways operate.

Can I use this approach to troubleshoot issues with per-profile gateways?▼

Yes, you can use this approach to troubleshoot issues with per-profile gateways. The process involves diagnosing the s6-overlay supervision tree and customizing the run-script for the specific per-profile gateway to correct its execution behavior.