codex - 💡(How to fix) Fix write only sandbox doesn't work inside a container

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

It should just work without a sandbox error. It should ask me for permission though if I've set to untrusted.

Root Cause

I'm running codex inside of a podman container, so I suspect the nested bwrap is conflicting. I do NOT want to run privileged because I don't want to give codex more perms. I do want it to write normally as if I had disabled the inner sandbox. I don't want to disable the sandbox for anything other than file writes.

RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

codex-cli 0.131.0

What subscription do you have?

pro

Which model were you using?

gpt-5.5

What platform is your computer?

Fedora Linux 43

What terminal emulator and version are you using (if applicable)?

bash

Codex doctor report

What issue are you seeing?

I'm running codex to try and avoid annoying approvals for writes in the workspace:

codex --sandbox workspace-write --ask-for-approval untrusted

If I ask it to write a TEST file I see:

Would you like to make the following edits? Reason: command failed; retry without sandbox?

And if I do yes, codex often writes python scripts that just write to files. This is completely insane and is wasting a ton of tokens.

I'm running codex inside of a podman container, so I suspect the nested bwrap is conflicting. I do NOT want to run privileged because I don't want to give codex more perms. I do want it to write normally as if I had disabled the inner sandbox. I don't want to disable the sandbox for anything other than file writes.

What steps can reproduce the bug?

Open codex cli inside a podman container by running: codex --sandbox workspace-write --ask-for-approval untrusted. Ask it to write a TEST file.

What is the expected behavior?

It should just work without a sandbox error. It should ask me for permission though if I've set to untrusted.

Additional information

NOTE: This used to work just fine, but broke in some recent update within the last 2 months or less I believe.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix write only sandbox doesn't work inside a container