From 04bec0d2c746541a33219f8f797a63c3d89d4f5c Mon Sep 17 00:00:00 2001
From: AutonetSellCar Deploy <autonet@grantech.kr>
Date: Mon, 5 Jan 2026 23:32:28 +0900
Subject: [PATCH] docs: Add manual/auto deployment conflict warning
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- Document git hook vs manual docker run conflict issue
- Add resolution steps for container name conflicts
- Reinforce: always use docker-compose for staging

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---
 CLAUDE.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/CLAUDE.md b/CLAUDE.md
index a49d880..fe2f737 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -118,6 +118,24 @@ ssh server2 "cd /opt/autonet/staging && docker compose -f docker-compose.staging
 docker run -v /opt/autonet/staging/backend/uploads:/app/uploads ...
 ```
 
+### ⚠️ 수동 배포와 자동 배포(git hook) 충돌 문제 (2025-01-05 추가 사례)
+
+**문제**: 수동으로 컨테이너를 만든 후 git push하면 자동 배포가 실패함
+
+**원인**:
+- 수동 배포: `docker run --name autonet-frontend-staging ...` → docker-compose가 관리하지 않음
+- 자동 배포: `docker compose down` → 수동 컨테이너는 중지되지 않음
+- 자동 배포: `docker compose up` → 컨테이너 이름 충돌로 실패
+
+**해결 방법**: 수동 컨테이너가 있으면 먼저 제거
+```bash
+# 충돌 시 수동 컨테이너 제거 후 docker-compose 재실행
+ssh server2 "docker stop autonet-frontend-staging autonet-backend-staging 2>/dev/null; docker rm autonet-frontend-staging autonet-backend-staging 2>/dev/null"
+ssh server2 "cd /opt/autonet/staging && docker compose -f docker-compose.staging.yml up -d"
+```
+
+**예방책**: 스테이징 배포는 **항상** docker-compose만 사용하고, 수동 docker run 절대 금지!
+
 ## ✅ 배포 전 필수 검증 명령어
 
 ```bash