A few days ago I woke up to one of my dockers not running, Trying to restart, it gave me an "Execution error - Container doesn't exist" When I tried to remove & recreate the Docker, bond0 was no longer available to set the docker on its own IP. Also noted Bond0 is no longer available on any of my dockers, I have had to turn of Bonding in order to allow for manual assignment of IP's to my dockers.

 

The server has been running bonded with no issues for a few months now.

 

I have the following error when enabling bonding & then docker:

Aug 15 13:12:39 Tower root: Error response from daemon: network dm-31b59fc8085d is already using parent interface bond0

I had posted in the Docker section & Pihole support page, but I don't know if its related to something else, as this is effecting all my docker's, not just the one container. I have a second server that has no issues running bonded (balancerr) & these same containers when tested. 

 

 

tower-diagnostics-20170815-1327.zip

Did you see my earlier answer ?

Sorry I didnt....I have removed & recreated the Docker, but still have the same error. I will try again.

1 minute ago, clowrym said:

Sorry I didnt....I have removed & recreated the Docker, but still have the same error. I will try again.

 

You need to delete the docker image.

 

Stop the docker service (see settings -> docker), after the service is stopped, you have the possibility to delete the image and recreate it.

Sorry, I missunderstood, I will try and remove the image, not just the container!!

Thanks for the help, Back up and running. Is this caused by something specific? I was gone for the weekend when it happened & hadn't had any access to the server to see anything suspicious.