docker-config-qa-regressionlisted
Install: claude install-skill aksheyw/claude-code-learned-skills
# Docker Config Change QA & Regression Pattern
**Context:** After modifying Docker container config, volume mounts, or environment variables — systematic verification to catch cascading failures
## Problem
Docker config changes (volume mounts, env vars, compose edits) can cause cascading failures that aren't immediately obvious. A config fix can break auth, lose credentials, or disconnect services. Without systematic QA, you discover these in production.
## Solution — QA Regression Checklist
Run this systematic check after ANY docker-compose.yml or config change:
### Phase 1: Container Health
```bash
# Container running?
docker ps --format 'table {{.Names}}\t{{.Status}}\t{{.Ports}}' | grep <name>
# Clean startup? (no errors)
docker logs --tail 30 <container> 2>&1
# Errors since latest start only (filter by timestamp)
START_TIME=$(docker inspect <container> --format '{{.State.StartedAt}}' | cut -c1-19)
docker logs <container> 2>&1 | awk -v ts="$START_TIME" '$0 >= ts' | grep -iE 'error|fail|crash' || echo 'CLEAN'
```
### Phase 2: Volume Mounts
```bash
# All mounts present?
docker inspect <container> --format '{{range .Mounts}}{{.Source}} -> {{.Destination}} ({{.Type}})
{{end}}'
# Host and container in sync?
diff <(md5sum /host/path/config.json) <(docker exec <container> md5sum /container/path/config.json)
```
### Phase 3: Credentials & Auth
```bash
# Auth profiles exist?
docker exec <container> find / -name 'auth-profiles*' -o -name 'credentials*' 2>/dev/null
# API