title: Failed to start docker-daemon: Firewalld: docker zone already exists
body: <p>I have the following after running <code>firewall-cmd --get-active-zones</code></p>
  <pre><code>public
    interfaces: virbr0 docker0 lxcbr0 wlan0
  trusted
    sources: 172.17.0.0/16 53.0.0.0/8
  </code></pre>
  <p>These are insights I got from <a href="https://stackoverflow.com/questions/65213831/failed-to-start-daemon-error-initializing-network-controller-error-creating-de">failed to start daemon: Error initializing network controller: Error creating default &quot;bridge&quot; network</a></p>
  <p>The problem is, <code>sudo dockerd</code> fails with error messages, among which there is</p>
  <pre><code>failed to start daemon: Error initializing network controller: Error creating default &quot;bridge&quot; network: Failed to program NAT chain: ZONE_CONFLICT: 'docker0' already bound to a zone
  </code></pre>
  <p>How to manipulate the zone so that I can start the docker daemon?</p>
  <p>EDIT: This solution worked for me:</p>
  <pre><code>sudo firewall-cmd --permanent --new-zone=docker 
  sudo firewall-cmd --reload
  sudo firewall-cmd --permanent --zone=docker --add-interface=docker0
  </code></pre>