March 12, 20188 yr I'm trying on a different unraid box to assign dockers to eth1 (br1) to slap on a vlan and do not see it as an option in the "Network Type:" drop down. In network settings, I have both tried to assign eth1 a static address and without and it did not work. I also tried to delete the docker image and the following commands to no avail: rm /var/lib/docker/network/files/local-kv.db /etc/rc.d/rc.docker restart Config: docker network ls NETWORK ID NAME DRIVER SCOPE 5e393f387db1 br0 macvlan local 4d7afeedc2bb bridge bridge local 128e42f37133 host host local a62254b82c56 none null local docker network inspect br1 [] Error: No such network: br1 ifconfig | grep -i br1 br1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 Anybody have any thoughts on how to unlock the mystery of the br1 macvlan interface?
March 12, 20188 yr Configuration wise everything looks alright. What happens if try to add manually. Ah, I see the problem... Your br0 is defined as 192.168.3.87/16 which overlaps with br1. Change br0 to 192.168.3.87/24 Edited March 12, 20188 yr by bonienl
March 12, 20188 yr Author 11 minutes ago, bonienl said: Configuration wise everything looks alright. What happens if try to add manually. docker network create -d macvlan --subnet=192.168.10.87/24 --gateway=192.168.10.1 -o parent=br1 br1 docker network create -d macvlan --subnet=192.168.10.87/24 --gateway=192.168.10.1 -o parent=br1 br1 Error response from daemon: Pool overlaps with other one on this address space Does not seem to work. I will remove the br1 bridge in network settings and do the following, perhaps would help. docker network create -d macvlan --subnet=192.168.10.0/24 --gateway=192.168.10.1 -o parent=eth1 br1 I seem to have stumbled upon this sort of thing a little while ago, I believe deleting the docker image helped. I have a similar setup on an older esxi box working and I'm able to see the br1 network type but for whatever can't get it to work here. Edited March 12, 20188 yr by joelones
March 12, 20188 yr I updated my response, because I saw a little later why it is not working. You need to stop the docker (and VM) service, then change your network settings for eth0 and put the mask on 24.
March 12, 20188 yr Author 9 minutes ago, bonienl said: I updated my response, because I saw a little later why it is not working. You need to stop the docker (and VM) service, then change your network settings for eth0 and put the mask on 24. Thanks. Yeah not sure how that got there. I was going to change it but I'm doing a netcat from another unraid box and was scared changing it would kill the network. Edited March 12, 20188 yr by joelones
Archived
This topic is now archived and is closed to further replies.