Solving Docker Network Problems in Fedora
Oct 6, 2020 · 1 minute read · CommentsLinuxFedoraDockerNetworkEnglish
After more than 12 years using Debian as a workstation, I decided to migrate to Fedora a little over 6 months ago, when I changed the HD of laptop for an SSD, The first reasons for the decision to test Fedora was the native support for Luks to encrypt the disk during installation and the desire to learn a little more about RPM packages and the ecosystem from Red Hat.
The migration was super easy, as I always liked to use Gnome, since version 2, the interface was not a problem because both use Gnome Shell, and dealing with SELinux and FirewallD were facilitated using Cockpit. The only problem found was related to Docker, which for some reason, the containers and the build couldn’t access the internet.
Browsing on mailing lists and forums, I noticed that, as Docker creates a new interface through which it NATs for accessing the containers, it would need to add this new interface in the “Trusted” zone in firewalld, which can be done in a simple way, with the command:
# firewall-cmd --permanent --zone=trusted --add-interface=docker0
# firewall-cmd --reload
When I restarted the docker service, both, build and containers internet access worked correctly.
Para editar este post basta clicar aqui.