Vynlovanth

Something in the GUI must not have saved in the back end then because I did have bond0 ticked in Settings -> Docker. That's why I was confused because I followed the process in the release notes exactly and everything looked correct in the GUI other than the networks available to the individual Dockers. I had macvlan next to "Docker custom network type:" as well. Either way, I upgraded to Unraid 6.12.8 and just repeated the process. It works now as expected on macvlan. All of my containers connected to bond0 get an IP address, are online, and show up in my Unifi dashboard now. Just have to keep an eye on it for a bit to make sure I don't see any call traces or crashes.

Already have my pro license so I’m largely unaffected until I need another license, but just wanted to say I’m glad the top license is still an unlimited device lifetime update license. Too many services depend on subscriptions (or other regular monthly/yearly fees of sorts to maintain features), and I understand it’s because ongoing updates require continuous streams of revenue but that’s a hard thing to swallow for home use. Personally I’m more than happy to pay more for the lifetime license, pro was already a good deal. I do worry about long term consequences as people buy their 1 year license, never update, then 3 years down the road want to update because of a new feature they heard about and they’re skipping multiple versions to do so. The accessibility of Unraid already lends itself to more casual users who don’t understand the importance of staying relatively up to date with Unraid OS (and don’t bother reading release notes) and I don’t think this will help. Other posters mentioned concerns about maintaining security of an Unraid install that is outside the 1 year support as well.

@BurntOC Nope I didn't, I'll try again on 6.12.7 and 6.13 when they release but the behavior I experienced is consistent.

Running Unraid 6.12.6 on my server, previously on an older version I had run into the macvlan call trace crashing my server, so I had changed my docker network configuration to ipvlan. I'd prefer to switch it back to macvlan to get better data in my Unifi setup if the call traces aren't an issue anymore. I followed the steps in the 6.12.4 release notes to disable bridging on eth0 and host access to custom networks is enabled, docker network type was auto changed to macvlan. When I start my array, my containers that were previously attached to "custom: br0" network interface are now attached to "None". I edited one of the containers in the Unraid GUI and the only network types available are Host, Bridge, or None. I assume I should see a custom: bond0 (I am using bonding) as an option here? My subnet is configured next to "IPv4 custom network on interface bond0:" in Settings -> Docker. I am not really sure what I am missing or where to go with this? I know in the meantime I can revert back easily to ipvlan and my containers automatically start back up with the prior custom: br0 network, just can't figure out where I'm going wrong with the macvlan solution. unraid-diagnostics-20240102-1501.zip

Curious about this as well and I wouldn't classify that as "all explained". Increased memory usage doesn't seem like a reason to revert unless it's a memory leak and don't know what these "other issues" are...

This poll ends up being a bit of a "Where are you from?" question, because most of the payment methods are country specific. Of course Apple Pay is going to be the most popular one, and I would definitely use it. But the Apple Pay option should probably include Google Pay as well.