Skip to content

Added a workaround in dev docs running-the-code.md to switch firewall backend to iptables

Christian Walgenbach requested to merge dev-docs-firewall-fedora32 into master

What does this MR do?

I recently upgraded to the Fedora 32 Beta release. I've had a great time so far but there is one minor pain point that took me a bit of time to figure out: Docker Compose containers can't talk to each other anymore.

After a bit of research it turns out the answer is simple: Fedora is now defaulting to nftables for firewalld1. Don't ask me what that actually means, I have no idea. Until then, that is why Docker Compose containers aren't able to talk to each other: the new format of these firewall rules is not observed by Docker, so therefore the traffic is blocked even within the containers.

This MR update the dev docs for a workaround to switch the firewall backend return to iptables.

How confident are you it won't break things if deployed?

very

Links to related issues

https://yunity.slack.com/archives/C1T1ZM9A4/p1586775001364300

Tests

No needed. It's only update for the dev docs.

Checklist

  • added a test, or explain why one is not needed/possible...
  • no unrelated changes
  • asked someone for a code review
  • joined #foodsharing-beta channel at https://slackin.yunity.org
  • added an entry to CHANGELOG.md (description, merge request link, username(s))
  • Once your MR has been merged, you are responsible to update the #foodsharing-beta Slack channel about what has been changed here. They will test your work in different browsers, roles or other settings
Edited by Chris Oelmueller

Merge request reports