moby--moby/libnetwork/firewall_others.go at 72c4a7b4969acbe5f8fd8dafbeb4481d9d856586 - kotovalexarian-likes-github/moby--moby - Forgejo by Causa Arcana

kotovalexarian-likes-github/moby--moby

mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00

Su Wang fcb70a0e86 DOCKER-USER chain not created when IPTableEnable=false.

This fix addresses https://docker.atlassian.net/browse/ENGCORE-1115
Expected behaviors upon docker engine restarts:
1. IPTableEnable=true, DOCKER-USER chain present
   -- no change to DOCKER-USER chain
2. IPTableEnable=true, DOCKER-USER chain not present
   -- DOCKER-USER chain created and inserted top of FORWARD
      chain.
3. IPTableEnable=false, DOCKER-USER chain present
   -- no change to DOCKER-USER chain
      the rational is that DOCKER-USER is populated
      and may be used by end-user for purpose other than
      filtering docker container traffic. Thus even if
      IPTableEnable=false, docker engine does not touch
      pre-existing DOCKER-USER chain.
4. IPTableEnable=false, DOCKER-USER chain not present
   -- DOCKER-USER chain is not created.

Signed-off-by: Su Wang <su.wang@docker.com>

2019-11-12 16:32:42 +00:00

6 lines

138 B

Go

Raw Blame History

 // +build !linux
 package libnetwork
 func setupArrangeUserFilterRule(c *controller) {}
 func arrangeUserFilterRule()                   {}