hermes-s6-container-supervision

Manage Hermes Agent container supervision with s6-overlay and cont-init.d workflows.

Updated May 11, 2026
One-click install
npx skills add https://github.com/jason660519/Project-Manager --skill hermes-s6-container-supervision-jason660519
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hermes-s6-container-supervision
Source: https://github.com/jason660519/Project-Manager/tree/main/hermes-agent/optional-skills/devops/hermes-s6-container-supervision
Command: npx skills add https://github.com/jason660519/Project-Manager --skill hermes-s6-container-supervision-jason660519

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide structured guidance to manage Hermes Agent container supervision using the s6-overlay, enabling reliable startup, graceful restarts, and consistent per-profile gateway behavior inside the Docker image.

Core Features & Use Cases

  • Guidance to add or remove static services that Hermes should supervise at container start (e.g., the dashboard).
  • Troubleshooting steps for per-profile gateway startups, restarts, and reconciling gateway state after docker restarts.
  • Explanation of cont-init.d boot scripts, UID/GID remapping, and the architecture choice of using a CMD-based main process (Architecture B) with s6 supervision.
  • Best practices for modifying run scripts and gateway routing without breaking Hermes workflows.

Quick Start

Explain how to enable a new static service in Hermes' Docker image and diagnose a failing gateway startup using s6-overlay.

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 manage Docker container supervision with s6-overlay in Hermes?

s6-overlay provides Hermes containers with reliable process supervision by running a CMD-based main architecture that handles init scripts, UID/GID remapping, and graceful service restarts.

How do I add static services to Hermes container startup using s6-overlay?

Adding static services to Hermes involves configuring s6-overlay supervision scripts to launch the service at container start, ensuring it initializes correctly during the cont-init.d boot sequence alongside existing profile gateways.

Why does my Hermes gateway startup fail after a Docker restart?

Hermes gateway startup failures often occur due to un-reconciled gateway states after Docker restarts. Troubleshooting involves checking the s6-overlay boot sequence and reconciling per-profile gateway supervision to restore routing.

What is the role of cont-init.d scripts in Hermes container boot sequencing?

cont-init.d scripts in Hermes execute one-time initialization tasks during container boot, such as UID/GID remapping and setting up environments, before the CMD-based runtime architecture routes user commands to gateways.

Can I modify s6-overlay run scripts without breaking Hermes workflows?

Yes, you can modify s6-overlay run scripts safely by following best practices that maintain the CMD-based runtime architecture and per-profile gateway routing, preventing disruptions to Hermes user command workflows.

Does Hermes support per-profile gateway slots with s6-overlay supervision?

Hermes supports per-profile gateway slots by using s6-overlay supervision to isolate and manage each profile's gateway state, ensuring consistent routing and startup behavior across Docker container restarts.