| View previous topic :: View next topic |
| Author |
Message |
toralf
Developer
Joined: 01 Feb 2004
Posts: 3922
Location: Hamburg
|
 Posted: Thu Jun 23, 2022 4:27 pm Post subject: avoid that dockerd creates a bridge iface at 172.x.x.x |
 |
|
I do have | Code: | # cat /etc/docker/daemon.json
{
"bip": "9.100.0.1/24",
"default-address-pools":[
{"base":"9.201.0.0/16","size":24},
{"base":"9.202.0.0/16","size":24}
]
}
|
but get that 172. bridge interface:
| Code: | t44 ~ # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.178.1 0.0.0.0 UG 2 0 0 enp0s25
9.100.0.0 0.0.0.0 255.255.255.0 U 0 0 0 docker0
172.18.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-14307ef5c8b5
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
192.168.178.0 0.0.0.0 255.255.255.0 U 2 0 0 enp0s25
|
What is the culprit ? |
|
| Back to top |
|
 |
spica
Apprentice
Joined: 04 Jun 2021
Posts: 285
|
| Posted: Sun Aug 06, 2023 5:10 am Post subject: |
|
|
If you require a fresh IP address on br-*, you must recreate the bridged network.
In my opinion, this outcome is understandable since the docker0 default network is controlled by the docker daemon, leading to the allocation of a new IP address. The bridged network is established externally, and from Docker's standpoint, the responsibility for maintaining the correct bridged network settings lies with the other side. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
