mj-agent-infra-docker-compose

Manages the mj-agent Docker Compose stack lifecycle across dev, test, and prod profiles.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/MJ-AgentLab/mj-agent --skill mj-agent-infra-docker-compose-mj-agentlab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mj-agent-infra-docker-compose
Source: https://github.com/MJ-AgentLab/mj-agent/tree/main/.claude/skills/mj-agent-infra-docker-compose
Command: npx skills add https://github.com/MJ-AgentLab/mj-agent --skill mj-agent-infra-docker-compose-mj-agentlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operating the mj-agent independent Docker Compose stack (mj-agent, mj-agent-postgres, mj-agent-redis) requires choosing the correct -f file chain per profile, running pre-checks against the mj-system network, and diagnosing failures like port conflicts, unhealthy containers, or Harbor pull errors. This Skill standardizes the full up/ps/logs/down lifecycle so operators avoid mis-loaded profiles and destructive mistakes. ## Core Features & Use Cases - Profile-aware lifecycle commands: Runs up, ps, logs, and down with explicit -f chains for dev (base + override), test, and prod overlays per ADR-025 4-file layering. - Pre-flight validation: Verifies mj-system-backend-network exists, mj-system biz postgres is healthy, .env secrets are present, and host ports 8001/5433/6379 are free before starting. - Troubleshooting matrix: Maps common failures (port conflicts, healthcheck timeouts, network not found, Harbor pull denied, proxy-related curl 502) to concrete fixes. - Use Case: A developer says "起 mj-agent compose" on a test host; the Skill runs pre-checks, executes the test-profile up command, verifies healthchecks and port listening, and reports a structured lifecycle report. ## Quick Start Ask the agent to start the mj-agent compose stack in dev profile and verify all three containers are healthy.

Frequently Asked Questions about mj-agent-infra-docker-compose

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

FAQPage Schema
How do I start a Docker Compose stack with multiple -f override files?▼

Pass each file explicitly in order: docker compose --env-file .env -f base.yml -f override.yml up -d. The mj-agent stack uses this pattern for dev, test, and prod profiles because auto-loading of override.yml does not apply when the base file is specified with -f from a subdirectory.

How do I check Docker Compose container health and logs?▼

Run docker compose -f <files> ps to see status and healthcheck results, and docker compose -f <files> logs --tail=100 <service> for recent output. The mj-agent stack expects mj-agent and mj-agent-postgres to report healthy and ports 8001/5433/6379 to be listening.

Why does docker compose fail with network not found for an external network?▼

The error occurs when an external: true network like mj-system-backend-network does not exist on the host. Start the mj-system stack first so its postgres is healthy and the network exists, since mj-agent only attaches as a consumer.

Why does curl to localhost return 502 while the container is healthy?▼

The host shell proxy variables (HTTP_PROXY/HTTPS_PROXY) route localhost through a system proxy such as Clash or v2ray. Use curl --noproxy '*' or set NO_PROXY=localhost,127.0.0.1,::1; the container itself does not need a restart.

When should I avoid docker compose down -v?▼

Avoid down -v unless you explicitly accept data loss, because it deletes the mj-agent-postgres and mj-agent-redis volumes including langgraph memory checkpointer data. This Skill treats it as a Level C destructive operation requiring explicit user confirmation.