hermes-s6-container-supervision

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides the necessary operational knowledge to debug, extend, and manage the s6-overlay supervision tree within the Hermes Agent Docker environment, ensuring reliable service lifecycle management.

Core Features & Use Cases

  • Service Management: Add or remove static services and manage per-profile gateway lifecycles.
  • Diagnostic Support: Troubleshoot container boot issues, UID/GID remapping, and service crash loops.
  • Architecture Guidance: Understand the main-program pattern and how to correctly interface with the s6-overlay supervision system.

Quick Start

Use the hermes-s6-container-supervision skill to inspect the status of a specific profile gateway service running inside the 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 add a static service to an s6-overlay supervision tree in a Docker container?

To add static services to the s6-overlay supervision tree, you modify s6-rc service definitions and utilize cont-init.d hooks to manage the service lifecycle within the Docker container.

Why does my s6-overlay container boot script fail during service initialization?

Container boot script failures often stem from incorrect main-wrapper.sh execution patterns, UID/GID remapping conflicts, or misconfigured s6-rc service definitions causing crash loops during initialization.

How does the main-wrapper.sh execution pattern interface with the s6-overlay supervision system?

The main-wrapper.sh execution pattern serves as the main-program entry point, coordinating the s6-overlay supervision tree to ensure robust service lifecycle management for the Hermes Agent Docker image.

Can I use s6-rc to reconcile per-profile gateway lifecycles inside a Docker image?

Yes, you can use s6-rc to reconcile per-profile gateway lifecycles by modifying the s6-overlay supervision tree to manage specific gateway services running inside the Docker container.

What is the best way to troubleshoot service crash loops in an s6-overlay environment?

The best way to troubleshoot s6-overlay service crash loops is to inspect s6-rc service definitions, verify cont-init.d hooks, and debug the main-wrapper.sh execution pattern to identify lifecycle management failures.

Do I need to understand cont-init.d hooks to manage the s6-overlay supervision tree?

Yes, understanding cont-init.d hooks is required to manage the s6-overlay supervision tree, as they execute container boot scripts and ensure proper service initialization within the Docker environment.