Fix COMMAG Compose write permissions - #63
Merged
Merged
Conversation
vtavakkoli
marked this pull request as ready for review
August 14, 2026 08:26
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Root cause
The COMMAG GitHub Actions job created bind-mounted host directories as the runner user, but the COMMAG Compose services kept the image UID (
10001). The non-root container therefore could not create/workspace/data/raw/commag/....Fix
commag-prepare,commag-train, andcommag-testtoLOCAL_UID:LOCAL_GIDincompose.override.yaml./artifactsfor the training and validation services, matching the existing real-data servicesdocs/COMMAG.mdThis retains non-root execution and avoids
sudo, root containers, or world-writable directories.Validation
pytest -q: 26 passedgit diff --check: passedThis is a follow-up to merged PR #62, whose COMMAG job exposed the permission mismatch.