v1.5 sandbox regression: bwrap loopback fails on GitHub Actions runner
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 170
- PR merge metrics
- No merged PRs in 30d
Description
Symptom
When pinning uses: openai/codex-action@v1.5 (instead of @v1), the action posts a comment on the PR saying it cannot read any files:
Не могу выполнить ревью в текущей сессии: любые локальные команды (`git diff`, `cat`, даже `pwd`) падают с ошибкой песочницы:
bwrap: loopback: Failed RTM_NEWADDR: Operation not permitted
So Codex returns a comment but cannot inspect the diff at all → no actual review.
Reproduction
- Pin
openai/codex-action@v1.5in any workflow - Open a PR
- Codex runs, posts the bwrap error message instead of a real review
@v1 (which currently floats to whatever pre-1.5 release was last published) works fine on the same repo, same runner.
Environment
- GitHub-hosted
ubuntu-latestrunner - Triggered on
pull_requestevent - Repository is private
- Same workflow file works on
@v1
Expected
v1.5 should be a non-breaking minor bump — but the bwrap sandbox cannot initialise its loopback interface, so the codex CLI inside cannot exec local commands.
Workaround
Stay on @v1 until v1.6 fixes the sandbox setup.
Related
- Workflow file: standard
pull_requesttrigger withopenai/codex-actionstep - Problem appeared the moment we changed only the
uses:line from@v1to@v1.5, then disappeared after revert.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the workflow file's pull_request trigger and openai/codex-action step, then reproduce the failure on an ubuntu-latest runner using @v1.5 and compare it with @v1. Inspect the v1.5 sandbox setup and runner permissions; done means the action can execute local commands and produce a real review without requiring the @v1 workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, linux
- Domain
- ci-cd, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100