Forumics logo Forumics
Issue 01

Back to issue

All Codex known issues

CLAIM C150 Supported 2026-11-17

GitHub issue #46110 in openai/codex, opened 2026-09-17 by harboriqdev, records a report that Codex 0.155.0-alpha.15 fails before executing any filesystem-restricted command on a native Ubuntu host when /proc/self/mountinfo contains valid nsfs entries created by snapd, with the error "error building bubblewrap command: mountinfo path is not absolute", because daemon_mounts.rs passes the mount root through mount_path(), which rejects any decoded path for which PathBuf is_absolute is false; the report was filed against Ubuntu 26.04.1 with bubblewrap 0.11.1 and snapd providing persisted mount namespaces under /run/snapd/ns.

Verbatim Excerpts from Cited Records
“Codex `0.155.0-alpha.15` fails before executing any filesystem-restricted command on a native Ubuntu host when `/proc/self/mountinfo` contains valid `nsfs` entries created by snapd.”
— harboriqdev · openai/codex (issue 46110 opening body, Summary section) · 2026-09-17T04:31:38Z ·GitHub Issue ↗
“The affected mountinfo entries have an `nsfs` root such as `mnt:[4026532835]`.”
— harboriqdev · openai/codex (issue 46110 opening body, Summary section) · 2026-09-17T04:31:38Z ·GitHub Issue ↗
“That is a valid Linux representation for a persisted mount namespace, but `codex-rs/linux-sandbox/src/daemon_mounts.rs` passes the mount root through `mount_path()`, which rejects any decoded path for which `PathBuf::is_absolute()` is false.”
— harboriqdev · openai/codex (issue 46110 opening body, Summary section) · 2026-09-17T04:31:38Z ·GitHub Issue ↗
“Valid `nsfs` mount roots such as `mnt:[...]` should not cause sandbox construction to fail.”
— harboriqdev · openai/codex (issue 46110 opening body, Expected behavior section) · 2026-09-17T04:31:38Z ·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 25 comments were read. The author (2026-09-17) confirmed the same source-level failure condition was still present on current main. cassandracomar (2026-09-17) attached a patch but could not open a PR as a non-collaborator. Multiple users confirmed the failure across Codex Desktop, the VS Code extension and WSL2, including Docker netns mounts, and several reported downgrading to an older bundled CLI or extension version as a workaround. No maintainer fix merged and no retraction of the original report appear in the surveyed thread. The claim documents only the original report, not a verified current state. Falsification probe: If GitHub issue #46110 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn. Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by scripts/verify_claim_verbatim.py.

See also: Codex vs Cursor head-to-head comparison on 9bests