[BUG] Claude cannot run when $HOME is read-only

Resolved 💬 7 comments Opened Mar 16, 2026 by PeterCDMcLean Closed May 6, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

I am attempting to execute Claude in a docker container when $HOME directory is volume mounted as read-only. plain Claude with no special options does not show any output and I must kill the container to stop the process. When giving --permission-mode bypassPermissions or --dangerously-skip-permissions, Claude shows the warning, but no amount of pressing enter will start the session.

If I restart the container with $HOME as read-write, Claude can start normally.

What Should Happen?

Claude should be able to run in a container when $HOME is read-only. Even if it's a command line option to supply a different read/writable location for .settings.json.

Error Messages/Logs

Steps to Reproduce

Create a Ubuntu24 docker container with whatever prerequisites to run Claude Code.

docker run --volume $HOME:$HOME:ro $HOME/.local/bin/claude ...

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.76

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 7 comments on GitHub. Read the full discussion on GitHub ↗