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.5 in 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-latest runner
- Triggered on
pull_request event
- 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_request trigger with openai/codex-action step
- Problem appeared the moment we changed only the
uses: line from @v1 to @v1.5, then disappeared after revert.
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:So Codex returns a comment but cannot inspect the diff at all → no actual review.
Reproduction
openai/codex-action@v1.5in any workflow@v1(which currently floats to whatever pre-1.5 release was last published) works fine on the same repo, same runner.Environment
ubuntu-latestrunnerpull_requestevent@v1Expected
v1.5should 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
@v1until v1.6 fixes the sandbox setup.Related
pull_requesttrigger withopenai/codex-actionstepuses:line from@v1to@v1.5, then disappeared after revert.