Why would you even use bubblewrap once it's running in a container? I've been running Codex in a container since it was publicly available, not even sure what you'd use bubblewrap for when you already separated codex from the rest of your filesystem?
I think neither the bundled bubblewrap nor the Ubuntu 24.04 bubblewrap works properly under Docker with the default options ... Yes, I've just tested that by asking Codex to "Test that bubblewrap is working properly" and then "Test again" after apt-get install bubblewrap.
EDIT: So the solution is to run "codex --dangerously-bypass-approvals-and-sandbox" in a Docker container?
cap_add:
- SYS_ADMIN
security_opt:
- seccomp:unconfined
- apparmor:unconfinedDoes it break anything? I didn't notice, I always run codex in "yolo" mode (the whole purpose of running it in docker).
If you need the sandboxing capabilities provided by the application and don’t want to run it on the host, you should set up a VM, not a container.
From a systems perspective, it’s foolish to rely on a proprietary application to provide its own isolation guarantees. This is an OS-layer responsibility.
ML/AI experts suffer badly from hubris. They are brilliant in one domain. It transfers poorly to systems engineering. The proof is in the FelonyBench results.
Even for developers working on Linux, you'll be surprised how many have never run a docker command in their life.
Or the long process to educate Windows users, and developers as well, to not run as Administrator.
With the recent security related events we already see that it seems to be wide spread practice that many operators avoid the hassle of isolating their agents.
It is just an incredible cultural experience to see how quick stupidity gets accepted as a behavioural default.