Container runs that cannot reach the host filesystem are no longer blocked for file deletions that only take effect inside the container.
Fixed
- Fixed
docker,podman, andnerdctlruncommands being blocked by local-filesystem rules such asrm.git-metadatawhen the container has no way to reach the host, so an idiom likedocker run --rm -w /tmp/app alpine sh -c 'rm -rf .git'now runs. (#366)- The container counts as isolated only when every
-v,--volume, and--mountis read-only and the run carries none of--volumes-from,--privileged,--pid,--userns,--device,--rootfs,--cap-add, a.sockmount, or a/runor/var/runmount. - Protections are unchanged everywhere else: writable mounts,
docker exec, unknown options beforerun, and words that could hide an option still get the full scan;git.push-*,network.*, andinterpreter.*rules still block inside an isolated payload; and thestrictsafety level, any custom rule naming a command in the payload, and an enabledrm.recursive-force-paranoidorinterpreter.one-liner-paranoidrule all keep every previous verdict.
- The container counts as isolated only when every