128 people reported
All time, since Sep 17, including 105 thumbs-up on GitHub.
Linux sandbox rejects host mounts
“The Codex VS Code extension cannot execute any sandboxed command.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/themes/145/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
4 bugs in this theme
- Sandbox mountinfo path errorNo workaround yet81 people
- WSL2 sandbox fails to startNo workaround yet36 people
- Sandbox socket mount isolation failsNo workaround yet10 people
- Sandbox fails on overmountsHas a workaround4 people
What's included
- Every sandboxed command and apply_patch fail with "error building bubblewrap command: mountinfo path is not absolute" when nsfs mounts from Docker or Snap are present
- On WSL2 with WSLg, the sandbox reports "app-server socket directory has an unsupported host mount at /mnt/wslg/distro"
- Under nix-user-chroot or on HPC nodes with an overmounted /tmp, bwrap fails with "Can't mkdir parents ... codex-daemon: Read-only file system" or an unsupported host mount error
- On Btrfs subvolume layouts, setup fails with "cannot establish app-server socket mount isolation"
- Appears after updating the desktop app, VS Code extension or CLI; codex sandbox /bin/true reproduces it
Not included
- Sandbox panic with ENOTDIR when a permission profile grants write access to individual files
- Commands that fail inside the sandbox after it has started
Original reports23, newest first
- Linux sandbox: covered mount aliases still passed to Bubblewrap in 0.164.0 and current main (#47455 regression)On GitHub#57520
- Linux: sandbox fails with “mountinfo path is not absolute”On GitHub#49732
- Title: Linux sandbox fails with Docker nsfs mounts: "mountinfo path is not absolute"On GitHub#48987
- VS Code extension in Ubuntu WSL2 fails to start bubblewrap sandboxOn GitHub#48976
- Bug: Bubblewrap sandbox fails on HPC with overmounted
/tmpOn GitHub#48758 - Problems after todays outage, VSCode/Codex can't do anythingOn GitHub#48329
- WSL2 sandbox rejects standard Snap nsfs and /mnt/wslg/distro mountsOn GitHub#48061
- WSL2 sandbox fails to start: unsupported host mount at /mnt/wslg/distroOn GitHub#48053
- Linux sandbox fails on Docker
nsfsmount with “mountinfo path is not absolute” in extension 26.917.62051On GitHub#47987 - Sandbox fails on WSL2 with WSLg: "app-server socket directory has an unsupported host mount at /mnt/wslg/distro"On GitHub#47849
Show all 23Show only the newest 10
mountinfo path is not absolutewhen running commands in shell environmentOn GitHub#47766- codex sandbox fails with cannot establish app-server socket mount isolation on Btrfs subvolume layoutOn GitHub#47708
- bubblewrap errorOn GitHub#47681
- VS Code agent sandbox fails before commands run: mountinfo path is not absoluteOn GitHub#47559
- WSL: Codex bubblewrap sandbox fails on nested /mnt/wslg/distro shared mountOn GitHub#47527
- WSL2 sandbox fails before command execution: unsupported host mount at /mnt/wslg/distroOn GitHub#47465
- Codex VS Code extension 26.917.61114 still fails with mountinfo path is not absolute on Linux with snapd nsfs mountsOn GitHub#47457
- Linux sandbox treats a fully overmounted mount as an app-server socket alias (breaks nix-user-chroot 2.x)On GitHub#47455
- [WSL2]
codex sandboxfails because/mnt/wslg/distrois reported as an unsupported host mountOn GitHub#47429 - Linux/Btrfs: sandbox rejects app-server socket mount when fstat device differs from mountinfoOn GitHub#47415
- Ubunthu ErrorOn GitHub#47368
- Bug: Linux sandbox fails with mountinfo path is not absolute after ChatGPT updateOn GitHub#47345
- Linux sandbox rejects valid nsfs mount roots from snapd:
mountinfo path is not absoluteOn GitHub#46110