10 people reported
All time, since Oct 5, including 9 thumbs-up on GitHub.
Sandbox bwrap cannot exec bash
“bwrap: execvp /bin/bash: No such file or directory”
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/3666/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 calls fail with bwrap execvp /bin/bash not found. Every Bash tool call fails immediately with the sandbox enabled, including trivial ones like echo hello, on a merged-usr layout where /bin is a symlink to usr/bin.
Is this your bug?
File my report- Where
- Bash tool sandbox
- Error text
bwrap: execvp /bin/bash: No such file or directory- Versions
- 2.1.289
- Platforms
- Linux
- How bad
- Stops work: a core feature can't be used.
Related: Linux sandbox fails every command
Not quite your bug?
- Sandbox fails on symlinked paths2 people
- Sandbox read-only bind breaks Bash3 people
- Sandbox apply-seccomp setgroups failure14 people
Original reports1, newest first
- bwrap: execvp /bin/bash: No such file or directory — sandbox completely broken on all merged-usr Linux distros (Debian/Ubuntu/Arch), still unfixed after 3+ prior reports (#41863, #69583, #88059, #64799)#99680