fix(hooks): keep pre-commit working tree host-owned #282

Merged

David merged 1 commit from fix/dev-371-precommit-host-owned-target into main

2026-06-19 10:00:47 +02:00

David commented

2026-06-18 17:20:00 +02:00

Owner

What

Mount the pre-commit cargo target cache at /cargo-target (outside the /build bind mount) and set CARGO_TARGET_DIR=/cargo-target, instead of nesting the named volume at /build/target. The volume name (dev-mokosh-apps-target-${USER}) is unchanged, so the cache still persists and is shared with just dev.

Why (DEV-371)

Nesting the named target volume under the /build bind mount makes the Docker daemon materialize a root-owned ./target/ directory on the host, which then needs sudo to remove and dirties the working tree. Pointing cargo at a sibling mount keeps the host working tree fully owned by the developer. This aligns with the governance Option A standard (target cache lives outside the source bind mount).

## What Mount the pre-commit cargo target cache at `/cargo-target` (outside the `/build` bind mount) and set `CARGO_TARGET_DIR=/cargo-target`, instead of nesting the named volume at `/build/target`. The volume name (`dev-mokosh-apps-target-${USER}`) is unchanged, so the cache still persists and is shared with `just dev`. ## Why (DEV-371) Nesting the named `target` volume under the `/build` bind mount makes the Docker daemon materialize a root-owned `./target/` directory on the host, which then needs `sudo` to remove and dirties the working tree. Pointing cargo at a sibling mount keeps the host working tree fully owned by the developer. This aligns with the governance Option A standard (target cache lives outside the source bind mount).

David added 1 commit

2026-06-18 17:20:00 +02:00

fix(hooks): keep pre-commit working tree host-owned

Check / clippy + fmt + tests (pull_request) Successful in 1m29s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

c204e32df5

Mount the cargo target cache at /cargo-target (outside the /build bind mount) and point cargo at it with CARGO_TARGET_DIR, instead of nesting the named volume at /build/target, which makes the Docker daemon create a root-owned target/ on the host that needs sudo to remove. The cache still persists in the named volume. Aligns with the governance Option A standard.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

#DEV-371