It seemed to be stuck in some sort of docker start loop.

Looked like they are starting, as in they were all seen, and some say starting, then it all seems to crash, It says Docker Services could not be started, then it repeats all that.

Everything else seems to be ok. Drives were good, both my bfs drives (cache and cache-nvme) looked right.

I through I did everything beforehand to remove and risks -

1 - Waiting a reasonable time.

2 - Checked the reports from others

3 - I am macvlan, with hardcoded IP addresses in my br0 network, so added the mac's to each of these in the extra parameters

4 - flas backup

5 - updated all dockers and plugins

also my other backup unraid system went to this with no issues.

Luckily, the rollback from the gui works (have to re-save a few containers to get them to start however). so the flash backup was not needed.

Diags attached if anyone can help, and what can I do ahead for a successful re attempt.

tower-diagnostics-20260619-1403.zip

I asked AI about all this and he said there were some issues with the xml's in my config.

These has some old config it said (eth0 etc), so I deleted them all.

The log suggested (it said) an issue with the Firefox container, so that was deleted, plus its cfg/bak files too.

I have a large cleanup of all the very old xml files and only ones that match a running container are there now.

While on that topic, I also got it to verify the Mac addresses with this command -

for file in /boot/config/plugins/dockerMan/templates-user/*.xml; do \
if grep -qE "<Network>br0(\.[0-9]+)?</Network>" "$file"; then \
name=$(grep -Po '(?<=<Name>)[^<]+' "$file"); \
mac=$(grep -Po '(?<=--mac-address=)[^ <"]+' "$file" || echo "⚠️ MISSING MAC ADDRESS"); \
echo -e "Container: $name\n -> MAC: $mac\n"; \
fi; \

It also suggested I should stop docker, delete the docker file, then re-create it and then re-create all my containers, as a final check - but that seems like a way overkill and you would frighten people off if that was a 'normal' instruction.

Maybe this: https://forums.unraid.net/topic/199000-docker-containers-with-netcontainerbinhex-delugevpn-not-starting-after-reboot/#findComment-1624462

49 minutes ago, JorgeB said:

Maybe this: https://forums.unraid.net/topic/199000-docker-containers-with-netcontainerbinhex-delugevpn-not-starting-after-reboot/#findComment-1624462

Nope - I don't have any like that.

I had on that pointed to a wg2 interface that no longer existed, bit that is cleaned up with all the other work I did above.

Seems a load of tidying up on the old unused docker xml files (assisted by AI) was needed for this.

Todays upgrade went in fine.

AI commands to check all the cfg files and made some edits and deleted some.