codex - 💡(How to fix) Fix Can't create socket: Operation not permitted - Full Access [1 comments, 2 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#19217Fetched 2026-04-24 05:58:36
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×3commented ×1cross-referenced ×1unlabeled ×1
RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

0.124

What subscription do you have?

Plus

Which model were you using?

gpt-5.5

What platform is your computer?

Ubuntu

What terminal emulator and version are you using (if applicable)?

No response

What issue are you seeing?

<img width="871" height="155" alt="Image" src="https://github.com/user-attachments/assets/20c89a22-eb9e-4406-921f-bf10c35970ca" />

What steps can reproduce the bug?

Previously, up to version 0.118, it worked in Full Access mode without any issues. The last version I used was 0.118. I updated directly to 0.124, so I don’t know how it behaved in the versions in between.

permission denied while trying to connect to the Docker ... Redis

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

Downgrade to Codex CLI version 0.118 to potentially resolve the "permission denied" issue with Docker and Redis.

Guidance

  • The issue seems to be related to a change introduced between versions 0.118 and 0.124 of the Codex CLI, as the user reports it worked previously.
  • To verify the cause, try downgrading to version 0.118 and check if the issue persists.
  • If downgrading is not feasible, consider checking the permissions and configuration of the Docker and Redis setup to ensure they are correctly set up for the current version of Codex CLI.
  • The fact that it worked in Full Access mode without issues up to version 0.118 suggests that the problem might be related to changes in how permissions are handled in newer versions.

Notes

The provided information does not include details about the expected behavior or additional context that could help pinpoint the exact cause. Therefore, the suggestion to downgrade is based on the information that it previously worked and the error message indicating a permission issue.

Recommendation

Apply workaround: Downgrade to version 0.118, as it is known to work and allows for temporary resolution of the "permission denied" issue while further investigation into the cause and a permanent fix can be pursued.

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

codex - 💡(How to fix) Fix Can't create socket: Operation not permitted - Full Access [1 comments, 2 participants]