5 ms·

Bubblewrap gets a bit confused inside a Docker container. If anyone knows how to run Codex inside a Docker container on Linux without it constantly complaining

• embedding-shape 1mo ago
  > If anyone knows how to run Codex inside a Docker container on Linux without it constantly complaining about a broken bubblewrap, please tell. 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?
  • ab71e5 1mo ago
    Doesn't it automatically use bwrap if it's installed (in the container in this case)?
    • krzyk 1mo ago
      Don't install bubblewrap? I didn't and use codex in docker.
      • bloak 1mo ago
        "Codex could not find bubblewrap on PATH. Install bubblewrap with your OS package manager. See the sandbox prerequisites: ... Codex will use the bundled bubblewrap in the meantime." 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?
        • eadwu 1mo ago
          cap_add: - SYS_ADMIN security_opt: - seccomp:unconfined - apparmor:unconfined
          • Phemist 1mo ago
            This kills the isolation.
        • krzyk 1mo ago
          What do you mean by "bundled bubblewrap nor the Ubuntu 24.04 bubblewrap works properly under Docker with the default options"? Does it break anything? I didn't notice, I always run codex in "yolo" mode (the whole purpose of running it in docker).
• sh34r 1mo ago
  You have to add Linux capabilities to support creating nested namespaces. IIRC SYS_ADMIN is required. If you do that, what do you think you’re achieving with the container? It defeats the entire purpose IMO, just makes development more inconvenient. 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.