fix: data volume owned by root broke reply capture (EACCES) - #2
Conversation
The image never created /app/data, so the named volume initialized root-owned while the app runs as USER node — every reply write failed. Create data/ in the image so the volume seeds with node ownership, and make capture() survive a broken store (log + drop instead of surfacing as a polling error). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 50 minutes and 9 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
The image never created /app/data, so the named volume initialized
root-owned while the app runs as USER node — every reply write failed.
Create data/ in the image so the volume seeds with node ownership, and
make capture() survive a broken store (log + drop instead of surfacing
as a polling error).
Co-Authored-By: Claude Fable 5 noreply@anthropic.com