April 6, 20251 yr I am still having problems with my docker containers on a VLAN not being accessible outside of the unraid. I have a VM on the same VLAN which works fine from outside Unraid and which can talk to docker containers on Unraid in the same VLAN. I am still using macvlan but made changes as described here: https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces. But still nothing. I also saw that if you don't use correct CIDR on the DHCP Pool it would break, but 172.16.16.128/25 should be correct, right? Anyone have any ideas?
April 6, 20251 yr Community Expert 4 hours ago, Tomo82 said: I am still having problems with my docker containers on a VLAN not being accessible outside of the unraid. I have a VM on the same VLAN which works fine from outside Unraid and which can talk to docker containers on Unraid in the same VLAN. I am still using macvlan but made changes as described here: https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces. But still nothing. I also saw that if you don't use correct CIDR on the DHCP Pool it would break, but 172.16.16.128/25 should be correct, right? Anyone have any ideas? In v7 the macvlan bug has been fixed... Unraid default configuration uses br0 bridging eth0 to the bridge... I would recommend returning back to using unraids default network settings: and using macvlan only if you require it. There is nothing wrong with ipvlan... Macvlan: https://docs.docker.com/engine/network/drivers/macvlan/ IpVlan: https://docs.docker.com/engine/network/drivers/ipvlan/ SO ... Please review earlier forum posts... I would need extra data to assist... docker network ls to confirm if other docker networks are made.... (If not we will need to rerun the docker network create command to fix...) aslo noted earlier in forum... ip a to show the interface and its link for correct vlans. And can tell me what vlans if any... please see earlier in form of teh noted issues when upgrading v6 to v7.... On 1/16/2025 at 8:07 AM, dchadd said: I believe he is saying since we were using a non-standard CIDR you need to switch the last digit of the DHCP range to a 0. For instance for 192.168.20.50 would switch to 192.168.20.0. AS CIDR is important as in v6 didn't write nor check the network config correctly. as stated in your docker setting with vlans. they need to be x.x.x.0 for dhcp to correctly use that network. ? is preserve on as you may need to recreate the docker network...
July 19, 2025Jul 19 On 1/14/2025 at 1:23 AM, bmartino1 said:Thank you for the additional data... Would still need to know other docker settings. as it appear you need to make the docker networks again...you really need to have the presve user defined networks enabled! ... As again I don't think you had that setting enabled before the upgrade thus the docker db and network data was wiped...to fix this, enable that setting for future updates to not break again. and remake your docker networks.Per your picture that setting seems to be enabled. per other data, you have interface with vlans corectly. the defualt custom eth in the picture is vlan1 to make a docker network and use the subnet on a vlan you need to make a docker network. since your network settings are bridging off and bonding off (same as me). you need to make a docker interface with the parent and tell dockers to use that network. as per picture: don't have a docker netwokr only eth0 gets a defuaut docker network...to fix this make docker network: # VLAN 10: Subnet 172.16.10.0/24, Gateway 172.16.10.1 docker network create \ --driver macvlan \--subnet=172.16.10.0/24 \--gateway=172.16.10.1 \ -o parent=eth0.10 \ macvlan_vlan10 # VLAN 20: Subnet 172.16.20.0/24, Gateway 172.16.20.1 docker network create \ --driver macvlan \--subnet=172.16.20.0/24 \--gateway=172.16.20.1 \ -o parent=eth0.20 \ macvlan_vlan20 # VLAN 25: Subnet 172.16.25.0/24, Gateway 172.16.25.1 docker network create \ --driver macvlan \--subnet=172.16.25.0/24 \--gateway=172.16.25.1 \ -o parent=eth0.25 \ macvlan_vlan25 run the above command then edit the docker and you will see macvlan_vlan## and select that if you want that docker on that vlan. thats it.I don't know what failed, what setting, or if you had previous docker corruption that is fixed or reset with the upgrade. but in my testing it involved around the docker setting preserver user defined... which is why I recommend upgrading to 6 stable then 7... as some setting were not introduced from 6.9 due to the macvlan bug...I just updated from version 6.12 to 7 and I have preserved setting enabled in Docker!! I had docker containerns running on a specifik VLAN and after upgrade all those containers can not start.I tried to update Plex container because of this issue (thought it would need an update to work or something) and the whole container disappeared!! I certainly don't hope the data of it is gone..This just happened and I have not been able to see how much of a loss it is. I have several very important containers running on another VLAN that is now not working at all right after the upgrade.Such a disaster upgrade! This just causes a lot of extra work and time!EDIT: Looks like the preserved setting suddenly was set to off. I can see the VLANS in the docker settings, but can still not see them in the container configs. Can not choose the correct VLAN for the container. Edited July 19, 2025Jul 19 by widdefmh
July 20, 2025Jul 20 Community Expert 18 hours ago, widdefmh said:I just updated from version 6.12 to 7 and I have preserved setting enabled in Docker!! I had docker containerns running on a specifik VLAN and after upgrade all those containers can not start.I tried to update Plex container because of this issue (thought it would need an update to work or something) and the whole container disappeared!! I certainly don't hope the data of it is gone..This just happened and I have not been able to see how much of a loss it is. I have several very important containers running on another VLAN that is now not working at all right after the upgrade.Such a disaster upgrade! This just causes a lot of extra work and time!EDIT: Looks like the preserved setting suddenly was set to off. I can see the VLANS in the docker settings, but can still not see them in the container configs. Can not choose the correct VLAN for the container.there was a known issue with how v6 wrote bad configs. even vlans with improper subnets broke. That forum that went over that is lost ont he4 forum.I would recomend starting the newto over witht eh net unraid v7 web UI.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.