Comment by embedding-shape

10 hours 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?

Doesn't it automatically use bwrap if it's installed (in the container in this case)?

  • Don't install bubblewrap? I didn't and use codex in docker.

    • "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?