False positive "Could not find bubblewrap on PATH" warning on Ubuntu 22.04 when bwrap is present and successfully executed
Open 💬 1 comment Opened May 31, 2026 by OkBayat
What version of Codex CLI is running?
v0.135.0
What subscription do you have?
pro
Which model were you using?
gpt-5.5 xhigh
What platform is your computer?
ubuntu
What terminal emulator and version are you using (if applicable)?
_No response_
Codex doctor report
What issue are you seeing?
Summary
Codex CLI v0.135.0 reports:
Codex could not find bubblewrap on PATH. Install bubblewrap with your OS package manager.
Codex will use the bundled bubblewrap in the meantime.
However, bwrap is installed, available on PATH, and Codex itself successfully executes it.
Environment
- Codex CLI: 0.135.0
- OS: Ubuntu 22.04.3 LTS
- bubblewrap: 0.6.1
$ command -v bwrap
/usr/bin/bwrap
$ bwrap --version
bubblewrap 0.6.1
Verification
Manual bubblewrap test succeeds:
bwrap --ro-bind / / --proc /proc --dev /dev --tmpfs /tmp /bin/sh -c 'echo bwrap-ok'
Output:
bwrap-ok
Evidence from strace
Codex checks and executes /usr/bin/bwrap:
access("/usr/bin/bwrap", X_OK) = 0
execve("/usr/bin/bwrap",
["/usr/bin/bwrap",
"--unshare-user",
"--unshare-net",
"--ro-bind",
"/",
"/",
"/bin/true"],
...)
Namespace creation succeeds:
clone(... CLONE_NEWNS|CLONE_NEWUSER|CLONE_NEWNET|SIGCHLD) = <pid>
No obvious EPERM/EACCES failure is present.
Expected behavior
No bubblewrap warning should be shown when:
/usr/bin/bwrapexistsaccess(..., X_OK)succeeds- Codex successfully executes
bwrap
Actual behavior
Codex still displays:
Codex could not find bubblewrap on PATH.
even though the binary is found and executed.
This appears to be a false positive or misleading startup warning.
What steps can reproduce the bug?
.
What is the expected behavior?
_No response_
Additional information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗