Hello!
I wasn't able to update some dockers for some days. when performing an update in the end i got the error "file exists".

yesterday i noticed that my nextcloud was offline and all four CPU on 100%. i stopped and restartet docker service.

the containers then startet again, CPU again on 100% and nextcloud still down (no errors on logs).

after a few minutes the whole docker section on the webUI vanished and on the docker site i got this error:

i tried a restart and suddenly everything seemed to work again. CPU on normal levels, dockers showing, nextcloud online.

after restart unraid started the parity check - unscheduled.

tried to update 2-3 dockers, still got the same error (file exists).

one day later i find nextcloud offline again, docker section hidden again and the same error as posted above. strange enough: all dockers seem to work - (don't know why nextcloud not reachable).

i can't post the exact update error because i can't start the update process because "Docker Service failed to start" and no containers showing.

in the attachment you can find diagnostics.

please help 🫠

datatower-diagnostics-20260504-0735.zip

Try recreating the docker image:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-file

Then:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications

Also see below if you have any custom docker networks:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks

thank you!

i got some dockers running again.

the most essential dockers don't start/work anymore.

nextcloud won't connect to mariaDB

MongoDB has a problem with locked file (so the unifi controller won't start).

edit: after reboot all docker containers have vanished again...

4 minutes ago, pika said:

edit: after reboot all docker containers have vanished again...

That suggests they are not on permanent storage. Post new diags with the array started.

i have rebootet another time (quite desperate...). should i post diagnostics without any container installed or should i install some containers, reboot, diagnostics?

edit: i have set them all up, and this time i got them all running. strange thing.

what can i do to be sure they won't all disappear on next reboot? in the attachment you can find acutal diagnostics (after re-installing all the containers and no reboot).

and another thing that seems strange: when i go to docker > docker size i get a total size of 19.1GB (Container) + 1.43GB (writeable) + 26.3MB (Log), but on the dashboard the Docker vdisk is on 99% (38.8GB / 40.0GB)?

datatower-diagnostics-20260504-2136.zip

Edited May 4May 4 by pika

System share appears to be on cache; reboot once more and post new diags if they disappear.

no more problems after reboot. strangest things happen 😅