--net=none lacks useful DNS options
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 875
- PR merge metrics
- No merged PRs in 30d
Description
None of the existing DNS options make any sense for containers where --net=none.
Can we get something like --dns=ignore or something, where it mounts an empty resolv.conf file and doesn't get creative with trying to do some magical right thing, and never refreshes based on the host resolv.conf.
This probably isn't the right solution, but there needs to be some kind of solution.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how --net=none handles the existing DNS options and how resolv.conf is created or refreshed. Clarify the desired behavior for an explicit DNS-ignore option, then define completion as a documented, tested behavior that avoids host resolv.conf updates for this network mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100