codex - 💡(How to fix) Fix linux-sandbox(bwrap) - GPU Access [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#23525Fetched 2026-05-20 03:48:30
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×3commented ×2closed ×1
RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

CLI

What feature would you like to see?

We would like for sandboxed agents to be able to run GPU-accelerated applications inside the sandbox, but there are two things missing at the moment to make that happen:

  1. The sandbox does not mount the various /dev points needed to access a GPU
  2. Our driver (libcuda.so) needs to know it is in a sandbox so that we can disable a few non-core features that have no way of working in bwrap but are fatal in a normal environment.

Another agent gives us a consistent env-var for this, but the Codex implementation of bwrap does not have anything that we can key off of.

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING