savarez-s6-container-supervision

Diagnose and debug s6-overlay container supervision for Savarez Docker images.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables developers and operators to modify, debug, or extend the s6-overlay supervision tree used by the Savarez AI Agent Docker image. It clarifies how to incorporate new services, diagnose gateway startup issues, and understand Architecture B's main-program pattern so container boot is predictable and maintainable.

Core Features & Use Cases

  • Projectable container supervision: configure, extend, and troubleshoot per-profile gateway supervision within the s6 framework.
  • Boot-time reconciliation: understand and modify the cont-init.d logic and profile gateway restoration to ensure gateway slots are correctly recreated across restarts.
  • Educational reference: provides architecture rationale, file mappings, and recommended workflows for debugging and extending the container image.

Quick Start

Connect to a running Savarez container and begin diagnosing a gateway startup issue using the documented s6-overlay workflow.

Frequently Asked Questions about savarez-s6-container-supervision

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

FAQPage Schema
How do I debug s6-overlay container startup issues in Docker?▼

To diagnose s6-overlay gateway startup failures, inspect the cont-init.d boot scripts and profile gateway reconciliation logic to ensure gateway slots are correctly recreated across container restarts.

How does the s6-overlay supervision tree manage container boot processes?▼

The s6-overlay supervision tree manages boot by enforcing an architecture where CMD runs the main program, while cont-init.d scripts handle initialization and per-profile gateway restoration for predictable startup.

Can I add new services to an existing s6-overlay Docker image?▼

Yes, you can extend an existing s6-overlay Docker image by incorporating new service definitions into the supervision tree and customizing cont-init.d boot scripts to ensure reliable startup.

What is the best way to customize UID remapping in s6 containers?▼

The best way to customize UID remapping in s6 containers is to modify the s6-overlay boot scripts and supervision configuration, ensuring the main-program pattern and per-profile gateways start reliably.

Why are my per-profile gateway slots missing after a Docker container restart?▼

Per-profile gateway slots are missing after a Docker container restart because the cont-init.d boot-time reconciliation logic failed to recreate them; verify the s6-overlay restoration scripts are correctly configured.

Does this s6-overlay supervision pattern work for production environments?▼

Yes, the s6-overlay supervision pattern works for production environments by enforcing predictable container boot behavior, reconciling gateway slots, and ensuring the main program runs reliably across contexts.