Sandboxed tool calls fail on Ubuntu 20.04 with bubblewrap 0.4.0 ('bwrap: Unknown option --argv0')

Additional diagnostic details from the affected machine:

$ codex --version
codex-cli 0.116.0

$ command -v bwrap && bwrap --version
/usr/bin/bwrap
bubblewrap 0.4.0

$ bwrap --help | rg -- '--argv0'
<no output>

$ dpkg -S /usr/bin/bwrap
bubblewrap: /usr/bin/bwrap

$ apt-cache policy bubblewrap
bubblewrap:
  Installed: 0.4.0-1ubuntu4.1
  Candidate: 0.4.0-1ubuntu4.1
  Version table:
 *** 0.4.0-1ubuntu4.1 500
        500 http://mirrors.aliyun.com/ubuntu focal-updates/main amd64 Packages
        500 http://mirrors.aliyun.com/ubuntu focal-security/main amd64 Packages
        100 /var/lib/dpkg/status
     0.4.0-1ubuntu4 500
        500 http://mirrors.aliyun.com/ubuntu focal/main amd64 Packages

A few practical observations:

• The failure is consistent for sandboxed tool execution paths.
• The error happens immediately at sandbox launch time, before the actual tool logic matters.
• Commands that bypass the normal sandbox path can still run successfully in the same environment.

That makes this look less like a repo-specific failure and more like a compatibility assumption in the sandbox wrapper: Codex appears to invoke bwrap with --argv0, but Ubuntu 20.04's packaged bubblewrap does not support that flag.

If helpful, I can also test a patched/local newer bubblewrap on the same machine and report whether that fully resolves the issue.

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• #15260

Powered by Codex Action

This also reproduces for me on Rocky Linux 8.10 via the VS Code extension’s bundled Codex (openai.chatgpt-26.318.11754-linux-x64, bundled codex-cli 0.116.0-alpha.10).

On this system, /usr/bin/bwrap --version is bubblewrap 0.4.0 and /usr/local/bin/bwrap --version is bubblewrap 0.9.0.

The error is the same: bwrap: Unknown option --argv0.

Downgrading the extension by one version avoids the issue. Restarting VS Code Server, changing PATH, and setting BWRAP / BUBBLEWRAP did not help.

Additional confirmed repro on Ubuntu 22.04 (Jammy):

• codex-cli 0.116.0
• system /usr/bin/bwrap from Ubuntu package bubblewrap 0.6.1-1ubuntu0.1
• after installing the system bubblewrap, sandboxed Codex tool calls started failing with bwrap: Unknown option --argv0
• removing the system bubblewrap package restored normal behavior by forcing Codex to fall back to its bundled bubblewrap

This suggests the incompatibility is not limited to Ubuntu 20.04 / bwrap 0.4.0; it also reproduces on Jammy with distro bubblewrap 0.6.1.

In this environment, the failure appeared immediately after upgrading to codex-cli 0.116.0 and installing the distro bubblewrap package.

use_legacy_landlock = true in .codex/config.toml workaround this.

use_legacy_landlock = true in .codex/config.toml workaround this.

Thanks, this did help on my WSL2 Ubuntu 22.04.5 setup with codex-cli 0.116.0, just to add two details in case anyone's unaware (I was at first at least):

1. The flag needed to be under [features]:

[features]
use_legacy_landlock = true

1. Putting it only in the repo-local .codex/config.toml fixed direct CLI runs in that repo for me, but the chat-integrated/sandboxed tool path still appeared to use ~/.codex/config.toml. So in my case I needed the same flag there as well.

Edit:
Codex CLI Code reviews still failing for me unfortunately.

• the integrated tool / review path still fails in my environment
• I still get unexpected argument '--sandbox-policy-cwd' there

so how we can fix this?

I compiled bwrap 0.11.0 from source and installed it to /usr/bin/bwrap. It seems to work.

Fun fact: apparently codex doesn't use PATH to find bwrap and just unconditionally uses /usr/bin/bwrap.

And the reason is known and due to AppArmor. The 0.115 build caused some issues to AppArmor users and the 0.116 build that fixed that is now causing issues to all of us using an older system version of bwrap due to older OS.

Since they mark other issues duplicate of this one, I'm sure they are well aware now and will find the middle ground in 0.117.

Use a newer bubblewrap and point /usr/bin/bwrap to it.

On Ubuntu 22.04, the system package was too old and did not support --argv0, which caused Codex/Coral sandboxed commands to fail with:

bwrap: Unknown option --argv0

Fix:

1. Build and install a newer bubblewrap to /usr/local/bin/bwrap
2. Replace the system path used by Codex:

sudo mv /usr/bin/bwrap /usr/bin/bwrap.0.6.1.bak
sudo ln -s /usr/local/bin/bwrap /usr/bin/bwrap

Verify:

/usr/bin/bwrap --version
/usr/bin/bwrap --help | grep argv0
codex sandbox linux /bin/true

Expected result:

• /usr/bin/bwrap reports the new version
• --argv0 appears in help
• codex sandbox linux /bin/true succeeds

Rollback if needed:

sudo rm /usr/bin/bwrap
sudo mv /usr/bin/bwrap.0.6.1.bak /usr/bin/bwrap

They still haven't fix this crap? Embarrassing

Downgrading to 0.115 fixed it on Linux Mint 21.3 (Ubuntu 22.04-based)

Possible Workaround (seems working at Ubuntu 22.04.5 LTS):
Manually install new one. Symlink the old one(bubblewrap 0.6.1) to the new one(bubblewrap 0.10.0).

sudo apt install -y libcap-dev libseccomp-dev meson ninja-build pkg-config
cd /tmp
wget https://github.com/containers/bubblewrap/releases/download/v0.10.0/bubblewrap-0.10.0.tar.xz
tar xf bubblewrap-0.10.0.tar.xz
cd bubblewrap-0.10.0
meson setup build --prefix=/usr/local
ninja -C build
sudo ninja -C build install
sudo ln -sf /usr/local/bin/bwrap /usr/bin/bwrap