fix(CICD) : 특정 테스트코드가 CI/CD 과정에서 배포 안되는 오류 수정#542
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the dev CI/CD GitHub Actions workflow to address CI failures where Testcontainers-based tests couldn’t access Docker during the pipeline run.
Changes:
- Added a workflow step to adjust
/var/run/docker.sockpermissions so Testcontainers can connect to Docker on the runner.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| # [추가] Docker 소켓 권한 부여 (Testcontainers가 접근할 수 있도록) | ||
| - name: Grant permission for Docker socket | ||
| run: sudo chmod 666 /var/run/docker.sock | ||
| shell: bash |
There was a problem hiding this comment.
sudo chmod 666 /var/run/docker.sock makes the Docker daemon socket world-writable. Even on ephemeral GitHub-hosted runners this is an avoidable escalation surface. Prefer a least-privilege approach (e.g., chgrp docker + chmod 660 on the socket and ensure the runner user is in the docker group), or use the officially supported Testcontainers/GitHub Actions setup that doesn’t require opening permissions to all users.
📝작업 내용
스크린샷 (선택)
API 응답 사진: (API 응답 스크린샷을 첨부해주세요.)
API 명세서 사진: (API 명세서 스크린샷을 첨부해주세요.)
테스트 커버리지 사진: (테스트 커버리지 스크린샷을 첨부해주세요.)
💬리뷰 요구사항(선택)
#️⃣연관된 이슈