TheOgre

Any idea? This is happening every single reboot. Just happened today, only workaround that works is Docker service > Disable, host access > disable, host access> enable, docker > enable. This is severely frustrating to have to do every single reboot. Please help lol

Hello all, been suffering with a really weird issue and can't seem to uncover what is going on. Each time I reboot my server, only SOME of my docker containers will start, it seems those using br0 all fail with Mar 28 12:44:13 Server rc.docker: nextcloud: Error response from daemon: failed to create the ipvlan port: device or resource busy Mar 28 12:44:13 Server rc.docker: Error: failed to start containers: nextcloud Mar 28 12:45:04 Server kernel: br0: Device is already in use. The only fix that works for me is, to disable the docker service, disable "Host access to custom networks", Apply, then enable "Host access to custom networks" and start the docker service, and then the containers start fine. I am using IPVLAN. Not sure where to go from here as there are no other log entries for it and googling produces no results. Any help? It's very frustrating having to do this on EVERY reboot of the server, and it seems like such a simple problem. ogreserv-diagnostics-20240328-2036.zip

Just would like to add to this thread that this has been an issue for a few people for a while including me and it is still occurring. No orphaned containers and nothing out of the ordinary here.

Just wanting to tag onto this thread, even after switching to ipvlan, the plugin is still detecting macvlan traces. Any way to diagnose why or anything else I need to do?

Just wanted to post an update here, I was also having this issue on 6.11 and just updated to 6.12.1 and was hoping this was one of the fixes, I had about 10 containers to update and using the update all function, I had the loop occur, only 2 loops and then it stopped but it still seems to be an ongoing issue. There seems to be numerous threads about this but haven't seen any unraid staff in any of them, anyway to make this more known as an issue? @Squid

Just updated to 6.12.1 and still having this issue. Anyone know what's going on or any fix for it?

So one issue I am running into is exclusions, I got the exclusions for each docker container figured out, but one big issue for me is the exclusion of the /.Recycle Bin/ folder from the Recycle Bin plugin. I find this plugin necessary for accidental deletion of files/folders and had it excluded in the old CA backup. I see under each docker container configuration there is an exclusion list and I can select basically any folder on the system from there, but will that actually propagate to the main backup? Seems a bit confusing as is. Any advice would be appreciated, thanks!

So I am actually running into a very similar problem. It seems that having more than just a few dockers running will crash my ISP modem. What's weird is that this hasn't been an issue for almost 3 months, where it last popped up then mysteriously disappeared. I have a few dockers running and everything is stable, but starting anymore than this will cause the modem to crash. Everything else in the network stays functional, all the Ubiquiti gear, routers, switches, but it's the ISP modem that is crashing. Following this thread to see if there's any helpful advice given here.

Was searching for the solution to this as well. The threshold is actually under Settings > Disk Settings > Default warning disk utilization threshold (%) Unfortunately this applied to every disk connected to the server, so your array and unassigned drives will be affected.

The docker image changes only if dockers add or update new images to it, this does not happen during normal operations. A memory leak will only cause RAM to increase, not the docker image.

This isn't related to memory usage but the size of your docker image. What's most likely happening is a docker is updating, at which point it expands the size of the docker image, then once completely updated, it clears the unnecessary parts of the image. Can resolve this by increasing the size of the docker image.

Very strange they vanished.... However yes, it should be the same process to get them all back if you haven't already.

I'm not sure if this will work but go to http://YOURSERVER/Docker/AddContainer as a URL and see if it will let you recreate the container from there, after that the others should stop rebuilding.

When you say "auto-rebuild" are you saying the page keeps refreshing and the container IDs keep changing on some of the other containers? That usually happens AFAIK when containers get names mixed up with their networking or something similar. If there are multiple containers doing it, might be best to restart the docker service and see if it continues or resolves.

On the docker page at the bottom, create a new container, then select the template drop-down and select binhex-qbittorrentvpn and it should repopulate all of your variables.