3 people reported

All time, since Sep 27, including 1 thumbs-up on GitHub.

Sandbox read-only bind breaks Bash

“Apparently the read-only bind for the allowRead parent is applied over the writable bind of the working directory, so the placeholder can't be created.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/1262/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Sandboxed Bash fails with read-only bind over working directory. A read-only bind for a parent path (allowRead entry or scrub denyWrite list) is applied over the writable workspace bind.

Is this your bug?

File my report
Where
Bash tool sandbox
Error text
bwrap: Can't create file /home/user/dev/parent/project/.claude/settings.json: Read-only file system
Versions
2.1.281 to 2.1.300
Platforms
Linux
How bad
Stops work: a core feature can't be used.

Part of: Linux sandbox fails every command3 bugs

  1. Sandbox apply-seccomp setgroups failure14 people
  2. Eval sandbox blocks workspace writes3 people

Not quite your bug?

  1. Sandbox fails on symlinked paths2 people
  2. Sandbox bwrap cannot exec bash10 people

Original reports2, newest first

  1. Sandbox: allowRead on a parent of the working directory breaks all Bash commands ("Read-only file system")#103955
  2. 2.1.281: CLAUDE_CODE_SUBPROCESS_ENV_SCRUB sandbox denies $HOME/actions-runner, so every Bash call fails on a default self-hosted GitHub Actions runner#97730

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.