5 people reported
All time, since Oct 6, including 3 thumbs-up on GitHub.
Reads fail in PID namespaces
“The /proc/${process.pid} path is either re-read in-process or passed to a child process such as pdfinfo, pdftoppm, or rg.”
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/3801/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
File reads fail inside PID namespaces without own procfs. PDF, image and .ipynb Read and single-file Grep reopen files via /proc/${process.pid}/fd instead of /proc/self/fd.
Is this your bug?
File my report- Where
- Read tool
- Error text
File does not exist- Versions
- 2.1.284 to 2.1.290
- Platforms
- Linux
Original reports2, newest first
- Read tool reports 'File does not exist' for images/PDFs inside a PID namespace: hardened read re-opens via /proc/${process.pid}/fd instead of /proc/self/fd (2.1.284–2.1.301)#102816
- Linux: PID namespace/procfs mismatch breaks PDF/.ipynb Read and single-file Grep, and can return another file's content#99853