-
Notifications
You must be signed in to change notification settings - Fork 18.7k
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
20.10.0-beta1@Fedora 33: Failed to program NAT chain: ZONE_CONFLICT: 'docker0' already bound to a zone #41609
Comments
Here is a related issue on redhat issue trackers: https://bugzilla.redhat.com/show_bug.cgi?id=1829090 A solution (that worked for me and others) is to delete the "/etc/firewalld/zones/trusted.xml" file. |
@arkodg ptal |
Was this an upgrade of an existing install of docker, or a fresh install? My primary suspect would be something with moby/libnetwork#2548, which should (having a quick look at the code) do a check if it's already added to the zone, but perhaps it's possible some detection fails if it was previously added manually 🤔 |
@Richard87 @arlyon thanks for raising the issue |
I was upgrading (reinstalling) to check out the new beta w/ cgroups2. |
Hi all! It was an upgrade, and I can confirm I changed docker0 to the trusted zone manually way back :) |
After rebooting, Docker/Moby complains about the docker1 bridge...
Edit: Created a new docker2 bridge, and starting using that as a super-quick-fix :) |
@Richard87 does removing the |
Tested the changes out on a CentosOS 8 Vagrant VM and I don't see any issues
Install Docker CE 20.10.0-beta1
Enable and Start Dockerd
Check Docker Zones and interfaces in firewalld
Reboot and again test it out
|
Hi! I have deleted everything I could find related to docker0/1/2, og restarted the computer 3 times, everything seems to work now! Thanks for all the feedback and help :) (Edit: Removed everything I created with brctl and deleted everything related to docker in fedoras Firewall gui) |
just install the docker-ce 20.10 on Fedora 33, need to remove /etc/firewalld/zones/trusted.xml in order to fix this issue... |
I don't think, you need to remove the whole /etc/firewalld/zones/trusted.xml file, but just the line with docker0 interface. You might have some other interfaces in this file, too. Like admun also commented, the "bug" is still existent in Fedora 33 docker 20.10 release. |
I've got a similar error after upgrading docker to version 20.10 on Fedora 32.
To fix this, I removed sudo firewall-cmd --get-zone-of-interface=docker0 | xargs -ri sh -c "sudo firewall-cmd --zone={} --remove-interface=docker0 && sudo firewall-cmd --zone={} --remove-interface=docker0 --permanent" Update 2022: |
actually, I am running into container failed to start after docker started... still looking for cause. |
@arkodg Can we detect this error and just log it instead of erroring out? |
Im trying to get that incorporated into the docs docker/docs#11883 |
Thanks for the workaround. In case anyone searching runs into this error:
The zone may be named differently from |
Restarting |
So glad I found this. Fixed my issues, too. Docker running again. phew. |
FWIW, I had to start firewall-config, and assign the |
I know this is already fixed but I been solving this for myself like once a month and aways come to this tread for copy paste :) so gonna part mine here too:
|
After installing Docker-20 Testing (fedora 32 package) on Fedra 33, it failed to start up because of some bridge configuration error.
When I manually created a new bridge named docker1, it worked nicely. Also running cgroups v2! :D
The debug log when it failed:
BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST
-->
Description
It fails to configure old bridge interface.
Steps to reproduce the issue:
Describe the results you received:
It should be able to configure the existing bridge
Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
Fedora 33 (upgraded from Fedora 32), cgroups v2
Running with custom bridge :)
brctl addbr docker1
daemon.json
adding"bridge: "docker1"
to the config fileThe text was updated successfully, but these errors were encountered: