For some reason when i update some of the docker containers i have (granted there are a lot of them with this issue, but not all or even half of them), the network they are assigned, some of them the custom bridge "br1", some of them "host" and some of them the default bridge, are changed to "none". tho it does not seem to happen to the containers i have using my custom macvlan network "bond0".

 

And i have to manually change it back to the network it had before updating. And next time there is an update to the container, the same thing happens.. over and over again..

 

The only thing i come of think of is that i think it started after i added another network card to the server and bonded the current and new card together (mode 4), but that might just be coincidence..

 

I created "diagnostics" before updating a container (in this case sonarr) and then a new set of diagnostics after it had updated and the network had changed to "none" and added those zip-files to the post here.

 

So, i guess im hoping someone here can help me solve this since its driving me insane at the moment. 

unraid-diagnostics-20250224-1138-AFTER_UPDATE.zip unraid-diagnostics-20250224-1137-BEFORE_UPDATE.zip

i might have been wrong regarding which containers were affected. i created a new user-defined (custom) bridge and removed the old one. so far the network hasnt changed to "none" on any of those that uses the new custom bridge network. and none of the containers with other network has had any issues since i created this post (so perhaps i was just imagining that the others were affected too)