GitHub issue #29908 in openai/codex, opened 2026-06-24 by legka, records a report that on Ubuntu 24.04 with Bubblewrap 0.9.0, apply_patch and ordinary managed sandbox commands fail before the requested command can run, with the error bwrap: loopback: Failed RTM_NEWADDR: Operation not permitted; the report attributes the failure to Bubblewrap sandbox setup, not repository file permissions, noting minimal Bubblewrap tests fail with uid-map and loopback errors under AppArmor unprivileged user namespace restrictions, and asks for the apply_patch and managed sandbox path to be made robust on Ubuntu systems with such restrictions or for a supported fallback that does not require changing host-wide security settings.
Verbatim Excerpts from Cited Records
“`apply_patch` and ordinary managed sandbox commands fail before the requested command can run.”
“The failure appears to come from Bubblewrap sandbox setup, not from repository file permissions.”
“`apply_patch` fails before it can read a file in the configured writable workspace.”
·
openai/codex (issue 29908 opening body, Observed behavior section)
·
2026-06-24T21:02:08Z
·GitHub Issue ↗
“The file-edit path is unusable because the sandbox helper depends on Bubblewrap/user namespace/network namespace behavior blocked by the host security configuration.”
·
openai/codex (issue 29908 opening body, Actual behavior section)
·
2026-06-24T21:02:08Z
·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 22 comments were read. github-actions[bot] (2026-06-24) flagged #29052 as a potential duplicate. legka (2026-06-24) adds that the coding workflow is effectively unusable when the sandbox fails, with unsandboxed approval as the only fallback; legka (2026-06-25) notes the failure is launch-context dependent, with managed workspace-write working when Codex was started from the VS Code integrated terminal. aixion1506 (2026-06-25, Codex CLI 0.142.0), dagassa (2026-07-01, Docker/devcontainer), antb123 (2026-07-14, 0.144.3), iJoshh (2026-07-15, 0.144.0), zizhong (2026-07-17, 0.144.5, bundled helper when the distro package was absent), YamabikoLab (2026-08-03, VS Code Dev Container on WSL2), sguanziroli-lgtm (2026-08-11, 0.147.0), lql341 (2026-08-25, 0.149.1), JerryZhong0910 (2026-08-27), Wendyrenlq (2026-09-04, managed enterprise workstation, non-admin), Jaehyeon-kr (2026-09-28, RunPod container), tanhaien (2026-10-08, 0.160.0), and StephenAlderman (2026-11-13, 0.167.2) independently reproduce the same Bubblewrap loopback and user-namespace failure family across Ubuntu 24.04 variants, containers, and cloud VMs. Workarounds reported: the documented Ubuntu 24.04 AppArmor bwrap-userns-restrict profile resolves it for dpritchett (2026-07-02 and 2026-07-06), cramjaco (2026-07-23), lql341 (2026-08-25), and StephenAlderman (2026-11-13), while madetotry (2026-08-08) reports the profile alone did not resolve it when Codex used its bundled Bubblewrap helper rather than the system binary; viyatb-oai (2026-07-06, OpenAI) pointed to the documented sandboxing prerequisites. The author later added a July 6, 2026 Applied devbox recurrence to the opening body, a different host-level trigger in the same failure family. No maintainer fix and no retraction of the report appear in the surveyed thread. The claim documents only the original report, not a verified current state.
Falsification probe: If GitHub issue #29908 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.