Tony Sleight

Thank you for the solution. What I hadn't seen before was the tick box for delete folder, which appeared this time when I booted up the server. Your solution to rebuild using overlay2 driver worked like a charm. Fortunately I had created a custom network interface called 'nextcloud-aio' so that was easy to change from the default bridged connection. Thank you very much for your help.

I have recently upgraded from Unraid 7.1.2 to version 7.1.4. Each time I startup, the docker service fails to start with the error 'failed to start containerd: timeout waiting for containerd to start'. I've looked through google and the forum threads here and cannot find a possible solution. The one thing I will say is that I am running the Docker service in Folder mode, not using the Vdisk. All solutions I have seen, refer to the vdisk version. Also, my disc pool is ZFS. I have worked with PCs since the early 1980s, so I am computer literate, however, I'm very new to Unraid and Linux as an operating system. I have attache the diagnostic zip file for your information. I have looked through the most obvious logs and all I can see is it reporting the docker daemon failed to start. I can't seem to see any error numbers or messages apart from the one above. Any help will be greatly appreciated as it was working great two days ago. My nexcloud service was up and running. tower-diagnostics-20251018-1213.zip