[7.2.1] Permission error when deleting local docker sandbox/workdir #22804
Labels
P2
We'll consider working on this in future. (Assignee optional)
team-Local-Exec
Issues and PRs for the Execution (Local) team
type: bug
Description of the bug:
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
This happens when I enable local docker execution, using --experimental_enable_docker_sandbox. Usually when I cancel a build using Ctrl-C. The broken state seems to persist, as all following builds fail the same way until I clear the _moved_trash_dir using sudo. It also happens when the build has been running for too long, or the _moved_trash_dir has not been cleared for a while.
Which operating system are you running Bazel on?
Linux 5.14.0-1052 #59-Ubuntu SMP x86_64 GNU/Linux
What is the output of
bazel info release
?release 7.1.2- (@non-git)
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.Patched version of nixpkgs bazel. None of the patch seem related to this issue.
What's the output of
git remote get-url origin; git rev-parse HEAD
?No response
If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
No response
Have you found anything relevant by searching the web?
Nope
Any other information, logs, or outputs that you want to share?
My initial assumption was that it was rules_nixpkgs related as copying files from the nix store copies readonly files that need careful handling to delete properly
chmod +rwx && rm
but looking at the content of that dir, I see root-owned subtrees that probably accumulate, which may explain why I also get the crash when the build goes on for too long.The content itself is also weird with all these zeroes. But maybe it's by design ?
The text was updated successfully, but these errors were encountered: