-
Notifications
You must be signed in to change notification settings - Fork 7.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firewalld integration #11883
Firewalld integration #11883
Conversation
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]>
✔️ Deploy preview for docsdocker ready! 🔨 Explore the source changes: c10041c 🔍 Inspect the deploy logs: https://app.netlify.com/sites/docsdocker/deploys/5fd75c7aca7edc000711e555 😎 Browse the preview: https://deploy-preview-11883--docsdocker.netlify.app |
should I also insert a |
network/iptables.md
Outdated
|
||
If you have [firewalld](https://firewalld.org) running on your system and are running Docker (with a version equal to or higher than `v20.10.0`) with `--iptables` enabled, Docker automatically creates a `firewalld` zone called `docker` and inserts all the network interfaces it creates (e.g. `docker0`) into the `docker` zone which allows for seamless networking | ||
|
||
**Note** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you have manually added a known Docker interface such as docker0
to a firewalld
zone (such as trusted
), and are experiencing any issues with starting the dockerd
daemon due to an error similar to:
failed to start daemon: Error initializing network controller: Error creating default "bridge" network: Failed to program NAT chain: ZONE_CONFLICT: 'docker0' already bound to a zone
Consider running the following firewalld
command to remove the docker interface from the zone.
# Please substitute the appropriate zone and docker interface
$ firewall-cmd --zone=trusted --remove-interface=docker0 --permanent
$ firewall-cmd --reload
Restarting dockerd
daemon inserts the interface into the docker
zone.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sgtm
Co-authored-by: Usha Mandya <[email protected]>
If I'm not wrong, masquerading and port forwarding is still done via iptables. Why isn't this specified in the documentation? |
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]