It should note that bridge interface may need to be added to a firewall zone with firewalld
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 4.7k
- Forks
- 8.5k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 108
Description
File: network/network-tutorial-standalone.md
This article should include warning that in some environments (e.g. firewalld on clean-install CentOS 8) user-defined bridge interface (which may be done via docker-compose) must be added to a zone using firewall-cmd.
Without a zone defined, firewalld will prohibit any communication between containers using that bridge.
Contributor guide
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
Read network/network-tutorial-standalone.md and review the section describing user-defined bridge networks. Add a warning explaining that environments using firewalld, such as a clean-install CentOS 8 system, may require the bridge interface to be added to a firewall zone; the documentation is done when this container-communication limitation and required firewall-cmd action are clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- documentation, networking
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100