Lost Docker Network Type bond0 & Custom IP Setting

[clowrym]

Woke up this Morning & PIhole Docker wasn't running. Trying to start it says "Execution error No Such container". Tried to remove & reinstall, but now I have also lost the ability to set an IP address in the docker unless I turn off Bonding (Which has been running with no issues). I can only set ip addresses if I turn off Bonding......Tried a reboot, removing & redoing bonding etc. , not sure what else to try!!

tower-diagnostics-20170808-1027.zip

[clowrym]

Through some testing this issue is across all my Docker containers, As soon as I turn Bonding back on, I lose the ability to set a custom IP in the network type dropdown.

[bonienl]

Your Docker log shows

level=error msg="Handler for POST /v1.29/networks/create returned error: network dm-31b59fc8085d is already using parent interface bond0"

Which means Docker finds interface bond0 already in use by a different container assignment. Unfortunately the only way to remove this existing (erroneous) assignment is by deleting and recreating the docker image. This requires containers to be re-installed again (their appdata isn't touched though), which may not be a bad idea anyway since the docker log complaints about several containers not found.