Ln 783 Container Launcher

Paths: File paths (shared/, references/, ../​ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root. If shared/ is missing, fetch files via WebFetch from https://raw.githubusercontent.com/​levnikolaevich/​claude-code-skills/​master/​skills/​{path}.

ln-783-container-launcher

Type: L3 Worker Category: 7XX Project Bootstrap

---

Purpose

Builds Docker images, launches containers, and performs comprehensive health verification using Docker native health checks and retry strategies.

Scope:

• Detect and validate docker-compose.yml configuration
• Build Docker images
• Launch containers with proper startup order
• Verify container health using native health checks
• Provide access URLs and cleanup instructions

Out of Scope:

• Building application code (handled by ln-781)
• Running tests (handled by ln-782)
• Container orchestration beyond single host (Kubernetes, Swarm)

---

When to Use

---

Workflow

Step 1: Pre-flight Checks

Verify Docker environment readiness.

Step 2: Parse Compose Configuration

Extract service information from docker-compose.yml.

Step 3: Build Images

Build all images defined in compose file.

Step 4: Launch Containers

Start containers with proper orchestration.

Step 5: Health Verification

Verify all containers are healthy using appropriate strategy.

Strategy Selection:

Retry Configuration:

Health Check Methods:

Step 6: Report Results

Return structured results to orchestrator.

Result Structure:

Container Status Object:

Health Check Result:

---

Error Handling

---

Options

---

Cleanup Instructions

Provide user with cleanup commands in report.

---

Critical Rules

1. Use native health checks when available - more reliable than external probes
2. Implement retry with backoff - services need time to initialize
3. Always collect logs on failure - essential for debugging
4. Parse compose file for ports - do not hardcode port numbers
5. Respect depends_on order - critical for database-dependent services

Monitor Integration (Claude Code 2.1.98+)

MANDATORY READ: Load shared/​references/​monitor_integration_pattern.md

For container health verification, use Monitor to stream container logs:

Use persistent: true if keepRunning is true and ongoing log monitoring is needed. Fallback: if Monitor is unavailable, use retry loop with sleep + curl health check.

---

Definition of Done

• Docker environment verified
• All images built successfully
• All containers running
• All health checks passing
• Access URLs provided
• Results returned to orchestrator

---

Reference Files

• Parent: ../​ln-780-bootstrap-verifier/​SKILL.md

---

Version: 2.0.0 Last Updated: 2026-01-10