Score:1

Docker creates additional bridge in wrong IP range

sh flag
Sim

I followed the answers here and changed the daemon.json to:

{
  "bip": "10.200.0.1/24",
  "default-address-pools": [
      { "base":"10.201.0.0/16","size":24 },
      { "base":"10.202.0.0/16","size":24 }
  ]
}

as I wanted to change the IP range used by the docker networking. However, when I start there is still a bridge created belonging to the IP range I wanted to move away from:

8: br-6c870af107ba: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:c0:ef:44:7e brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global br-6c870af107ba
       valid_lft forever preferred_lft forever

How can I prevent docker from creating this bridge interface?

Score:0
sh flag
Sim

Apparently docker has a restart resistant cashed config. You need to run docker network prune. Now the bridge is not created anymore and I successfully moved my IP range.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.