Repository navigation
bwrap: Can't mkdir .codex/memories: No such file or directory #13635
Description
What version of Codex CLI is running?
codex-cli 0.111.0
What subscription do you have?
Business
Which model were you using?
No response
What platform is your computer?
Linux 4.18.0-553.63.1.el8_10.x86_64 x86_64 x86_64
What terminal emulator and version are you using (if applicable)?
No response
What issue are you seeing?
I'm using Bubblewrap sandbox feature instead of Landlock, because my linux kernel doesn't support Landlock.
seeing codex tries to do └ bwrap: Can't mkdir .../.codex/memories: No such file or directory.
Was working ok a few days ago. Maybe related to f72ab43.
What steps can reproduce the bug?
Uploaded thread: 019cc029-c268-7b63-81fe-ff6cda8e2941
What is the expected behavior?
No response
Additional information
No response
Activity
github-actions commentedon Mar 5, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
/dev/urandomfrom bubblewrap sandbox #12056Powered by Codex Action
jif-oai commentedon Mar 6, 2026
This was fixed here: #13467. Will be part of the next release
Thank you
yitoli-c commentedon Mar 9, 2026
@jif-oai the same bwrap error still exists in v0.112.0.
uploaded thread: 019cd31d-6108-74b3-bf04-a54453640d4f
rebroad commentedon Mar 14, 2026
@jif-oai I am still getting this issue as of v0.115-0-alpha.19
rebroad commentedon Mar 14, 2026
@yitoli-c did you manage to find any workaround yet? Codex is always trying to use perl or python to edit files, and is often failing to do it correctly! The apply_patch tool was far more reliable!
yitoli-c commentedon Mar 14, 2026
@rebroad, the only "workaround" I could find to avoid this error is just give "full-access"... quite annoying.
Very useful finding about ~/.codex symlink set up in your issue! We also have similar setup. I just tried to remove symlink and apply_patch didn't give this bwrap error. Unfortunately removing symlink can't really be a workaround for me and my colleagues due to how the home dirs are setup.
I reported this same issue a few days ago again in #14261. Hope this problem get fixed soon because some of my colleagues are uncomfortable with "full-access", so codex became less usable to them.
yitoli-c commentedon Mar 17, 2026
the error no longer shows as of 0.115.0. seems to have been fixed.