Fix --iptables=false for Docker Swarm
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 875
- PR merge metrics
- No merged PRs in 30d
Description
In service_linux.go below functions uses IPTables APIs that might create/update IPChain.
fwMarker()
redirector()
programIngress()
If --iptables=false is set dockerd should not create any iptables rules or chains
https://github.com/docker/libnetwork/pull/2339 fixes part of the issue by checking the above flag before creating the DOCKER-USER chain
Raising this issue to track the fix for docker service
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 in service_linux.go by reading fwMarker(), redirector(), and programIngress(), then trace how the --iptables flag reaches these entry points. The fix is complete when docker service with --iptables=false creates no iptables rules or chains; the issue mentions no specific test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100