[Bug]: No network from container on MacOS 26
- Dominant language
- Swift
- Stars
- 49.9k
- Forks
- 1.8k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 22
Description
### I have done the following
- [x] I have searched the existing issues
- [ ] If possible, I've reproduced the issue using the 'main' branch of this project
### Steps to reproduce
```sh
$ container run --rm -it parrotsec/security:6 bash
# curl www.baidu.com
curl: (6) Could not resolve host: www.baidu.com
# dig www.baidu.com @114.114.114.114
;; communications error to 114.114.114.114#53: timed out
;; communications error to 114.114.114.114#53: timed out
;; communications error to 114.114.114.114#53: timed out
; <<>> DiG 9.18.33-1~deb12u2-Debian <<>> www.baidu.com @114.114.114.114
;; global options: +cmd
;; no servers could be reached
```
### Current behavior
Cannot connect to Internat from container.
### Expected behavior
Connect to Internat from container.
### Environment
```markdown
- OS: macOS 26.0 Beta (25A5327h)
- Xcode: 26.0.0.0.1.1754022347
- Container: container CLI version 0.3.0 (build: release, commit: 3fcf647)
```
### Relevant log output
```shell
$ container run --rm -it parrotsec/security:6 bash
# curl www.baidu.com
curl: (6) Could not resolve host: www.baidu.com
# dig www.baidu.com @114.114.114.114
;; communications error to 114.114.114.114#53: timed out
;; communications error to 114.114.114.114#53: timed out
;; communications error to 114.114.114.114#53: timed out
; <<>> DiG 9.18.33-1~deb12u2-Debian <<>> www.baidu.com @114.114.114.114
;; global options: +cmd
;; no servers could be reached
```
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Contributor guide
Assessment
This issue has not been assessed yet.