fix(devcontainer): preserve readonly compose mounts#767
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
📝 WalkthroughWalkthrough
ChangesRead-only mount propagation for Docker Compose devcontainers
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
3ddd7e6 to
a8a4145
Compare
a8a4145 to
88f0444
Compare
Summary
readonlyandromount options when devcontainer mounts are converted into generated Docker Compose service volumes.readonlyandrobecome read-only volumes while valued options likereadonly=trueremain unsupported.Root Cause
config.Mountstores mount options that are not modeled directly inOther. The non-compose Docker path serializes those options back into the mount string, but the compose override path rebuiltServiceVolumeConfigwith onlyType,Source, andTarget, droppingreadonly/robefore Docker Compose saw them.Validation
go test ./pkg/devcontainer/...Fixes #766.
Summary by CodeRabbit
Bug Fixes
readonly,ro, orreadonly=trueare now correctly marked as read-only in the generated service volumes.Tests
ReadOnlysettings.