fix: use named volume for ClickHouse to avoid permission issues in CI #916
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the ClickHouse CI test failure caused by permission denied errors when GitHub Actions'
setup-pythonaction scans the workspace for pip caching.The ClickHouse container was using a bind mount (
./clickhouse-data:/var/lib/clickhouse) which creates files with root ownership. When the CI runner (non-root user) tries to scan directories for pip caching, it fails withEACCES: permission denied, scandir '.../clickhouse-data/access'.This change switches to a named Docker volume (consistent with how
postgresandpgadminare already configured), which keeps the data in Docker's volume storage and avoids the permission issue.Review & Testing Checklist for Human
./clickhouse-datadirectlyNotes
Link to Devin run: https://app.devin.ai/sessions/cc081bf8267d4c2c831e339f0814bda5
Requested by: Yosef Arbiv (@arbiv)
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.