#3652 PR merged: run-in-docker source error

Labels: enhancement, ReaR Project

gdha opened issue at 2026-10-05 14:01:

Pull Request Details:

  • Type: Enhancement

  • Impact: Low

  • Reference to related issue (URL): n/a

  • How was this pull request tested? Interactive run
    $ tools/run-in-docker ubuntu:26.04 -- rear dump

  • Description of the changes in this pull request:

The Forbidden to source error was ReaR's secure-sourcing guard (is_trusted_write) refusing files that are writable by group or others. Your host umask of 0002 produces rw-rw-r-- files, and those permissions carry into the bind-mounted /rear tree inside the container.

Two changes made:

  1. Ran chmod -R go-w on the repo to clear the group/other write bits immediately.
  2. Added a permanent guard to tools/run-in-docker that runs chmod -R go-w "$rear_toplevel_dir" before the docker run loop, so this never recurs regardless of your umask or future checkouts.

codacy-production commented at 2026-10-05 14:02:

Up to standards ✅

🟢 Issues 0 issues >
> > **Results:** > `0` new issues > > [View in > Codacy](https://app.codacy.com/gh/rear/rear/pull-requests/3652/issues) >

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

gdha commented at 2026-10-29 15:30:

@rear/contributors When there are no objections would like to merge this PR by next week Friday (EOW)?

[Export of Github issue for rear/rear.]