scbe-docker-workflow
Coordinate SCBE Docker workflows from build to runtime. Use for SCBE container commands, docker-compose service startup, health checks, and troubleshooting of image/build failures, port conflicts, and
SKILL.mdresearch/sphere-grid/skills/scbe-docker-workflow/SKILL.md
GitHubSCBE Docker Workflow
Quick Start
- Change to repo:
C:\Users\issda\SCBE-AETHERMOORE-working
- Verify Docker files:
Dockerfiledocker-compose.ymldocker-compose.api.ymldocker-compose.unified.yml
- Run the standard command for your target stack:
- Single image:
npm run docker:buildthendocker run -it -p 8000:8000 scbe-aethermoore:latest - Single compose:
npm run docker:compose - API compose:
docker-compose -f docker-compose.api.yml up -d - Unified stack:
docker-compose -f docker-compose.unified.yml up -d
- Single image:
Standard Operations
- Build image:
docker build -t scbe-aethermoore:latest .docker build -t scbe-aethermoore .
- Run container directly:
docker run -it scbe-aethermoore:latest- Add port mapping when testing API locally, typically
-p 8000:8000
- Start compose stacks:
docker-compose up -ddocker-compose -f docker-compose.api.yml up -ddocker-compose -f docker-compose.unified.yml up -d
Health and Runtime Checks
docker psdocker logs <container>- Health check endpoints:
http://localhost:8000/v1/health(API-focused compose)http://localhost:8080/health(unified gateway and Dockerfile default health test)
docker ps -f health=unhealthyto spot failing healthchecks
Troubleshooting Playbook
- Build errors before compile step:
- Retry with
docker build --no-cache -t scbe-aethermoore:latest . - Check for transient network errors downloading build toolchains (Node/Python/liboqs)
- Retry with
- Container exits immediately:
docker logs <container>- Validate expected env vars from stack file and
.envusage
- Port conflicts:
- Check host ports
8000,8080, and3000are free before mapping - Use compose alternatives or remap ports in a temporary override
- Check host ports
- Compose startup stalls:
docker-compose logs -f- Confirm required service health using container logs and
docker ps -f status=running
Reference and Deep Context
For full stack maps, service-level expectations, and deeper remediation steps, read:
Automation Assets
Use the troubleshooting script when you need repeatable diagnostics:
scripts/scbe_docker_status.ps1assets/action-summary.template.yaml
Example usage:
.\scripts\scbe_docker_status.ps1 -RepoPath . -InspectStacks -ShowLogs.\scripts\scbe_docker_status.ps1 -RepoPath . -ContainerName scbe-core -LogTail 120.\scripts\scbe_docker_status.ps1 -RepoPath . -CleanRestart