deviantony / deviantony/docker-elk
Mention possible challenges with UFW and firewalld
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 18.4k
- Forks
- 6.9k
- Avg merge
- 7m
- Merged PRs (30d)
- 6
Description
A user reported issues running the stack due to firewalld blocking traffic on the elk bridge in #541. Another one reported similar problems in Gitter.
Similarly to what we did with SELinux, we should warn users about possible challenges using Compose on a machine running firewalld.
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
Review the existing SELinux guidance and the reports referenced in issues #541 and this issue. Add equivalent documentation warning about possible UFW and firewalld challenges when running the Compose stack; it is done when users are directed to relevant firewall considerations before deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100