sr-s6-container-supervision

Modify and debug s6-overlay supervision trees in SR Agent Docker containers.

2|1|Updated Jul 14, 2026

Search Tags:#devops #docker #container #gateway #supervision #s6-overlay

Ready to run

npx skills add https://github.com/heysuhas/hermes_cli --skill sr-s6-container-supervision

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sr-s6-container-supervision
Source: https://github.com/heysuhas/hermes_cli/tree/main/optional-skills/devops/sr-s6-container-supervision
Command: npx skills add https://github.com/heysuhas/hermes_cli --skill sr-s6-container-supervision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of managing service lifecycles, container boot sequences, and process supervision within the SR Agent Docker environment, ensuring reliable service uptime and correct container shutdown behavior.

Core Features & Use Cases

Service Supervision: Manage static and per-profile gateway services using s6-overlay v3.
Boot Reconciliation: Automate the restoration of profile gateway states and UID/GID mapping during container startup.
Architecture Debugging: Diagnose issues related to the main-wrapper pattern, s6-rc service slots, and container exit codes.

Quick Start

Use the sr-s6-container-supervision skill to inspect the status of all running profile gateways in the current container.

Frequently Asked Questions about sr-s6-container-supervision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage s6-overlay supervision trees in Docker containers?▼

s6-overlay supervision trees in Docker containers are managed by configuring static services, per-profile gateways, and container boot hooks to ensure robust service lifecycle management and reliable process uptime.

What is s6-overlay PID 1 process management and why do I need it?▼

s6-overlay PID 1 process management replaces the default Docker init process to handle signal propagation, reconcile persistent volumes, and ensure correct container exit codes during shutdown. It is needed for reliable service supervision.

How do I configure static services and per-profile gateways using s6-overlay v3?▼

Static services and per-profile gateways using s6-overlay v3 are configured by defining service slots within the supervision tree, automating the restoration of gateway states and UID/GID mapping during container boot reconciliation.

Why does my Docker container return incorrect exit codes on shutdown with s6-overlay?▼

Incorrect Docker container exit codes during shutdown with s6-overlay typically result from improper signal propagation through the main-wrapper pattern or misconfigured s6-rc service slots that fail to terminate processes cleanly.

How do I debug s6-rc service slots and the main-wrapper pattern in SR Agent containers?▼

Debugging s6-rc service slots and the main-wrapper pattern in SR Agent containers involves inspecting the s6-overlay supervision tree architecture to diagnose service lifecycle failures, boot hook execution, and profile gateway state restoration issues.

Does s6-overlay work with persistent volume reconciliation for Docker profile gateways?▼

s6-overlay works with persistent volume reconciliation by automating the restoration of profile gateway states and UID/GID mapping during container startup, ensuring boot sequences properly align service configurations with existing volume data.