init_firewall.sh fail at container start

Resolved 💬 1 comment Opened Jun 29, 2025 by guilhem- Closed Aug 7, 2025

What version of Codex is running?

0.1.2505172129

Which model were you using?

all

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64 / wsl2 / docker rootless / crun

What steps can reproduce the bug?

When running ./run_in_container.sh
I get:

Using domains from file: api.openai.com
Resolving api.openai.com...
Adding 162.159.140.245 for api.openai.com
Adding 162.159.140.245 for api.openai.com
ipset v7.17: Element cannot be added to the set: it's already added

What is the expected behavior?

No stop in container starting sequence.

What do you see instead?

Container is stopped on error.

Additional information

Multiple dns resolver produce duplicate in dig command.

node@af3c2bcd3664:/$ dig +short openai.com
172.64.154.211
172.64.154.211
104.18.33.45
104.18.33.45

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗