openai / openai/codex-action

v1.5 sandbox regression: bwrap loopback fails on GitHub Actions runner

Open
#88 0 comments 0 reactions 0 assignees View on GitHub

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

  1. Pin openai/codex-action@v1.5 in any workflow
  2. Open a PR
  3. 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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.