![]() In Docker Compose v2.0.0 it appears to silently continue using the old network configuration binding to 0.0.0. If you forgot to do this in Docker Compose v1, it printed an error saying the network settings in the project and the daemon were different and conflicted. NOTE/WARNING: Like in the comment, you need to delete your pre-existing Docker networks after applying this patch. + for name, conf in ems(): + if conf.driver and conf.driver != "bridge": + continue + conf.driver_opts = conf.driver_opts if conf.driver_opts is not None else + Networks = Network(client, name, 'default') I set my router to stop the DHCP range at 192.168.1.232 So my open range is 192.168.1.233 to 192.168.1.238 or 192.168.1.232/29 I create a macvlan network called home for this open segment on every docker host. a/compose/network.py +++ b/compose/network.py -256,6 +256,12 def build_networks(name, config_data, client): Then plan for the the docker application to use the the same IP regardless of which docker host is hosting the application. ".name": "docker0 ",Īnd that's explains that create a new network with the option ".host_binding_ipv4"="192.168.17.1" can solve this problem as well.ĭiff -git a/compose/network.py b/compose/network.py create a new sub interface tied to dot1q vlan 40 ip link add link eth0 name foo type vlan id 40 enable the new sub-interface ip link set foo up now add networks and hosts as you would normally by attaching to the master (sub) interface that is tagged docker network create -d ipvlan -subnet 192.168.40.0/24 -gateway 192.168.40.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |