Hello everyone,

 

when I upgraded from unRAID 6.11.5 to 6.12.2 I had to experience macvlan call traces causing my server to crash. I tried with 2-nic docker segmentation method for my containers (br0 → br1) but this did not help, macvlan call traces still occurred, so I downgraded back to unRAID 6.11.5.

 

 

Now I am looking for a solution to keep individual IP-addresses per Docker Container (right now it's br1) but I also would like to upgrade to the newer unRAID versions (latest stable for now is 6.12.4). Many of my containers look like that (with different IP):

 

 

 

I am confused about the solutions on how go to use unRAID 6.12.4 without getting macvlan call traces.

 

For me it is important that some docker containers have their own IP-Address since I can prioritize specific devices in my Fritzbox (for example the IP-address of a torrent container is low priority but the IP-address of a teamspeak is high priority). If I am understanding correctly, this does not work with ipvlan. But I also am using Docker Compose Manager with some stacks and some custom networks.

 

I have taken a look into the release notes:
https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces

 

 

Quote

For those users, we have a new method that reworks networking to avoid issues with macvlan. Tweak a few settings and your Docker containers, VMs, and WireGuard tunnels should automatically adjust to use them:

• Settings > Network Settings > eth0 > Enable Bonding = Yes or No, either work with this solution
• Settings > Network Settings > eth0 > Enable Bridging = No (this will automatically enable macvlan)
• Settings > Docker > Host access to custom networks = Enabled

Note: if you previously used the 2-nic docker segmentation method, you will also want to revert that:

• Settings > Docker > custom network on interface eth0 or bond0 (i.e. make sure eth0/bond0 is configured for the custom network, not eth1/bond1)

When you Start the array, the host, VMs, and Docker containers will all be able to communicate, and there should be no more call traces!

 

 

So when I follow these steps, will I still be able to give individual IP-addresses to my containers? After following these steps, will the IP-addresses stay the same or do I have to edit each container and setup the IP-address? Is there anything else to take care of except these steps (and the troubleshooting section)?

 

Thanks for reading into my questions!

/push

 

I'm worried about upgrading and need some help.

Should all be fine if you disable bridging for eth1.