So while jdupes was running after using automover plugin, my docker was suddenly corrupted. I don't know if it had anything to do with each other just that the corruption preceded jdupes starting. I am on unraid 7.2 diagnostics attached.

syslog-192.168.1.100.log

Edited November 3, 2025Nov 3 by Seraphys

Please post the diagnostics.

4 hours ago, JorgeB said:

Please post the diagnostics.

Attachedseraphys-diagnostics-20251103-0750.zip

I'm not seeing anything that suggests the Docker folder is corrupt, though I recommend using a Docker image instead; Docker folders can sometimes cause some strange issues.

There appears to be a container constantly restarting; you can typically find which one it is by looking at their uptimes.

4 minutes ago, JorgeB said:

I'm not seeing anything that suggests the Docker folder is corrupt, though I recommend using a Docker image instead; Docker folders can sometimes cause some strange issues.

There appears to be a container constantly restarting; you can typically find which one it is by looking at their uptimes.

The diag was unfortunately gotten after I had restarted. The syslog I attached in my first post had the errors. Isn't docker directory and overlay2 the current recommendation?

Edited November 3, 2025Nov 3 by Seraphys

I also don't see any issues with the cocker folder on the syslog.

2 minutes ago, Seraphys said:

Isn't docker folder and overlay2 the current recommendation?

If using a folder with zfs, overlay2 is the recommendation, but in general, using a Docker image is the default and what I recommend.

And check to see if there's a container restarting.

10 minutes ago, JorgeB said:

I also don't see any issues with the cocker folder on the syslog.

If using a folder with zfs, overlay2 is the recommendation, but in general, using a Docker image is the default and what I recommend.

And check to see if there's a container restarting.

Hmmm i only ask because ive seen posts by squid saying image is antiquated and shouldn't be used lol. I attached an image of the error i had captured before restarting. As for the docker restarts i have scripts for restarting stuff like the arrs cause they get borky after running a long time.

My recommendation would be to recreate the docker folder as docker image, typically less prone to issues, and when there are some, it's much easier to troubleshoot.