fix(docker): 매니저 서비스 restart 정책·depends_on 보강#46
Conversation
feat: sync api.yaml and fix api endpoints
mc-workflow-manager, mc-application-manager, mc-data-manager 등이 초기 기동 및 서버 재부팅 시 일부 올라오지 않는 문제 수정. 근본 원인 - 일부 서비스에 restart 정책이 없어, 무거운 의존 서비스(Jenkins/Nexus/ RabbitMQ/infra-manager/MariaDB)보다 먼저 떠서 크래시한 뒤 자력 복구 불가. - 재부팅 시 depends_on 순서는 적용되지 않고 restart 정책이 있는 컨테이너만 데몬이 자동 기동하므로, 정책이 없는 매니저들이 올라오지 않음. 변경 - mc-workflow-manager: restart: unless-stopped 추가, jenkins(healthy) 의존 추가 - mc-application-manager: restart: unless-stopped 추가, nexus/infra-manager (healthy)/rabbitmq(healthy) 의존 추가 - mc-application-manager-sonatype-nexus: restart: unless-stopped 추가 - mc-data-manager-db: restart: always 추가 (재부팅 시 DB 미기동 → data-manager 재시작 반복 문제 해결) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
AI Direct Commit Attribution BlockedThis pull request cannot be merged because it contains commits with AI tool attribution (Claude, Anthropic, GitHub Copilot, etc.) in commit message trailers (for example Why this is blockedIn open-source contributions, the human author is expected to create commits and open pull requests. Under current open-source license frameworks (DCO, Sign-off, CLA, etc.) AI-attributed commits may have unclear implications. Following the community proposal from 2026-05-08, until the project policy is finalized, AI direct commit signoff and co-authored-by records are prohibited in this repository. Matched commitsHow to fixMost recent commit only - strip the attribution trailers: git commit --amend --message="$(git log -1 --pretty='%s%n%n%b' | grep -vE 'Co-Authored-By:|Generated-By:|Assisted-By:|Co-Developed-By:')"
git push --force-with-leaseMultiple commits - use interactive rebase: git rebase -i HEAD~5
# Mark each commit as `reword` and remove the trailer lines in the editor
git push --force-with-leaseThe check will re-run automatically after the force-push, and the merge can proceed once the AI direct commit signoff and co-authored-by records are removed. Repository administrators may also enforce this check via Branch Protection rules. |
문제
./mcc infra run초기 기동 시, 그리고 서버 중단 후 재가동 시mc-workflow-manager,mc-application-manager,mc-data-manager등 일부 서비스가 올라오지 않음.원인
depends_on순서는 적용되지 않고, restart 정책이always/unless-stopped인 컨테이너만 자동 기동됨 → 정책 없는 매니저들이 안 올라옴.변경
restart: unless-stopped추가 +mc-workflow-manager-jenkins(service_healthy) 의존 추가restart: unless-stopped추가 +sonatype-nexus,mc-infra-manager(healthy),mc-observability-rabbitmq(healthy) 의존 추가restart: unless-stopped추가restart: always추가 (재부팅 시 DB 미기동으로 data-manager가 재시작만 반복하던 문제 해결)검증
docker compose config -q구문 검증 통과conf/docker/docker-compose.yaml1개 파일 (+13줄)참고
🤖 Generated with Claude Code