openclaw - 💡(How to fix) Fix Bundled Codex bwrap sandbox needs first-class AppArmor support or clearer diagnostics on Ubuntu 24.04+

Summary

On an AppArmor-enforcing Ubuntu 24.04 host, Codex-backed cron and agent runs can fail at the sandbox boundary before user code meaningfully executes. The failure mode appears to involve the bundled bwrap path and host policy interaction.

Actual behavior

In failing runs, the runtime launches a bundled bwrap sandbox and the session stops with permission errors before normal skill work completes. Observed errors include permission failures such as:

• bwrap: loopback: Failed RTM_NEWADDR: Operation not permitted

The practical result is that the job can look like a skill/runtime problem even though the blocker is sandbox bootstrap or host policy compatibility.

Expected behavior

One of these should happen:

• OpenClaw ships a working AppArmor profile or equivalent support for the bundled sandbox path
• install or upgrade flows detect the missing policy and warn clearly
• failing runs emit a first-class diagnostic that explicitly identifies AppArmor or sandbox policy incompatibility as the root cause

Why this matters

This failure happens before normal skill logic, so it is difficult to diagnose from the job summary alone. Operators can spend time debugging the wrong layer unless the runtime makes the host-policy dependency explicit.

Minimal repro

1. Use Ubuntu 24.04 with AppArmor enforcing
2. Run a Codex-backed cron or agent session that uses the bundled sandbox path
3. Observe the run fail at sandbox startup with Operation not permitted style errors before normal skill execution completes

Environment

• OpenClaw 2026.5.19
• Codex-backed runtime
• Ubuntu 24.04
• AppArmor enforcing

Note

If this is already tracked under an existing bwrap or AppArmor issue, this report can be treated as an additional reproducibility and UX signal rather than a separate root cause claim.