codex - 💡(How to fix) Fix Codex Fails to Run in WSL Ubuntu After Moving Its Location Due to Missing `/usr/bin/bash` [1 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#20189Fetched 2026-04-30 06:32:26
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3

Root Cause

When I have already moved the Ubuntu location in WSL, choosing WSL as the agent’s runtime location on Windows causes Codex to fail to run in Ubuntu because /usr/bin/bash is missing.

RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

0.126.0

What subscription do you have?

plus

What platform is your computer?

No response

What issue are you seeing?

When I have already moved the Ubuntu location in WSL, choosing WSL as the agent’s runtime location on Windows causes Codex to fail to run in Ubuntu because /usr/bin/bash is missing.

What steps can reproduce the bug?

When I have already moved the Ubuntu location in WSL, choosing WSL as the agent’s runtime location on Windows causes Codex to fail to run in Ubuntu because /usr/bin/bash is missing.

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

Update the Codex App configuration to use the correct path for the bash executable in the WSL environment.

Guidance

  • Verify that the /usr/bin/bash path is correct in the WSL environment after moving the Ubuntu location.
  • Check if the bash executable is installed and available in the WSL environment.
  • Consider setting the agent's runtime location to a different path or configuring the Codex App to use an alternative shell.
  • Investigate if there are any environment variables or configuration files that need to be updated after moving the Ubuntu location in WSL.

Notes

The issue seems to be related to the change in the WSL environment after moving the Ubuntu location, which affects the Codex App's ability to find the bash executable.

Recommendation

Apply workaround: Update the Codex App configuration to use the correct path for the bash executable in the WSL environment, as the issue is likely caused by the changed environment after moving the Ubuntu location.

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