hermes-s6-container-supervision

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

Updated May 24, 2026

Search Tags:#docker #container #profiles #gateway #entrypoint #supervision #s6

Ready to run

npx skills add https://github.com/anxiety135790/hermes-skills --skill hermes-s6-container-supervision-anxiety135790

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hermes-s6-container-supervision
Source: https://github.com/anxiety135790/hermes-skills/tree/main/software-development/hermes-s6-container-supervision
Command: npx skills add https://github.com/anxiety135790/hermes-skills --skill hermes-s6-container-supervision-anxiety135790

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you modify and debug the s6-overlay supervision layer inside the Hermes Agent Docker image, especially when container startup, profile gateways, or service lifecycle behavior is failing or unclear.

Core Features & Use Cases

Container supervision changes: Add, remove, or adjust static s6-rc services such as dashboard startup behavior.
Profile gateway debugging: Diagnose why per-profile gateways do not start, restart, or persist across Docker restarts.
Boot and entrypoint understanding: Explain the Architecture B pattern where the container CMD is the main program and user arguments flow through the wrapper correctly.
Reconciliation workflow: Work with cont-init boot scripts that remap ownership, seed files, and restore gateway service slots from persistent profile state.
Use case: You are updating the Hermes Docker image and need to ensure a new service is supervised correctly while preserving exit-code behavior and gateway recovery across container boots.

Quick Start

Ask me to inspect or modify the Hermes s6-overlay container supervision flow for a specific service, gateway, or boot-time behavior issue.

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 s6-overlay container supervision when a Docker service fails to start?▼

Debug s6-overlay container supervision by inspecting cont-init boot scripts and s6-rc service definitions to identify startup failures. You can trace static service registration, check run-script generation, and verify Docker exit-code behavior to locate the failing component in the Hermes Agent image.

Why does my per-profile gateway not persist across Docker restarts?▼

Per-profile gateway persistence fails when cont-init reconciliation scripts do not properly restore gateway service slots from persistent profile state. You need to ensure boot-time scripts correctly remap ownership and seed files so the s6-rc service manager can recover the gateway lifecycle.

How does the container entrypoint pass user arguments to the main program with s6?▼

The container entrypoint uses an Architecture B pattern where the container CMD is the main program and user arguments flow through the wrapper correctly. This ensures the s6-overlay supervision layer routes commands properly while maintaining service lifecycle management.

How do I add a new static service to s6-rc in a Docker image?▼

Add a new static service to s6-rc by creating service definitions and generating the corresponding service manager run-scripts. You must ensure the cont-init scripts handle boot-time reconciliation and that Docker exit-code behavior remains consistent for the supervised service.

Can I use s6-overlay to manage dashboard startup behavior in Docker containers?▼

Yes, you can use s6-overlay to manage dashboard startup behavior by adjusting static s6-rc services. The supervision layer allows you to add, remove, or modify static service definitions so the dashboard starts reliably within the container lifecycle.

What are the limitations of modifying s6-rc service definitions for Hermes Docker profiles?▼

Modifying s6-rc service definitions requires correct handling of cont-init scripts and Docker exit-code behavior, and errors can disrupt gateway recovery across container boots. You must preserve boot-time reconciliation and per-profile gateway lifecycle state to avoid service supervision failures.