Skip to content

Fix COMMAG Compose write permissions - #63

Merged
vtavakkoli merged 1 commit into
mainfrom
agent/fix-commag-compose-permissions
Aug 14, 2026
Merged

Fix COMMAG Compose write permissions#63
vtavakkoli merged 1 commit into
mainfrom
agent/fix-commag-compose-permissions

Conversation

@vtavakkoli

Copy link
Copy Markdown
Owner

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

  • map commag-prepare, commag-train, and commag-test to LOCAL_UID:LOCAL_GID in compose.override.yaml
  • bind-mount ./artifacts for the training and validation services, matching the existing real-data services
  • pass the GitHub runner UID/GID to every COMMAG CI invocation
  • document the portable Linux invocation in README and docs/COMMAG.md

This retains non-root execution and avoids sudo, root containers, or world-writable directories.

Validation

  • pytest -q: 26 passed
  • critical Ruff checks: passed
  • Python compileall: passed
  • workflow and Compose YAML parsing: passed
  • git diff --check: passed

This is a follow-up to merged PR #62, whose COMMAG job exposed the permission mismatch.

@vtavakkoli
vtavakkoli marked this pull request as ready for review August 14, 2026 08:26
@vtavakkoli
vtavakkoli merged commit 25d8027 into main Aug 14, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant