Skip to content

Commit 52fde1a

Browse files
arkodgusha-mandya
andauthored
Firewalld integration (docker#11883)
* Firewalld integration Added a section mentioning the firewalld integration and added notes on handling issues we've seen in the community Relates to docker/for-linux#1163 Signed-off-by: Arko Dasgupta <[email protected]> * Update network/iptables.md Co-authored-by: Usha Mandya <[email protected]> * Minor style edits Co-authored-by: Usha Mandya <[email protected]>
1 parent 681be44 commit 52fde1a

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

Diff for: network/iptables.md

+14
Original file line numberDiff line numberDiff line change
@@ -93,3 +93,17 @@ any address on the host. If you want to change that behavior to only
9393
expose ports on an internal IP address, you can use the `--ip` option to
9494
specify a different IP address. However, setting `--ip` only changes the
9595
_default_, it does not _restrict_ services to that IP.
96+
97+
## Integration with Firewalld
98+
99+
If you are running Docker version 20.10.0 or higher with [firewalld](https://firewalld.org){: target="blank" rel="noopener" class=“”} on your system with `--iptables` enabled, Docker automatically creates a `firewalld` zone called `docker` and inserts all the network interfaces it creates (for example, `docker0`) into the `docker` zone to allow seamless networking.
100+
101+
Consider running the following `firewalld` command to remove the docker interface from the zone.
102+
103+
```bash
104+
# Please substitute the appropriate zone and docker interface
105+
$ firewall-cmd --zone=trusted --remove-interface=docker0 --permanent
106+
$ firewall-cmd --reload
107+
```
108+
109+
Restarting `dockerd` daemon inserts the interface into the `docker` zone.

0 commit comments

Comments
 (0)