Been back to running all of my dockers (same ones I had running while getting the crashes) for 7 days now and zero crashes or unclean shutdowns.
No further system changes from my side, only things that would have changed are docker versions and plugin versions. Must have been something in there causing it. Whatever it was it seems resolved now by itself. Weird.
It is a 2xNVME pool...ended up doing this after a massive cache failure a year ago. I may re-examine it if this happens again.
I switched from a docker img aronud the time 6.9.0 came out because I was getting excessive writes to the cache pool and it did indeed fix it. Some folders ended up on the array during lastnight/this mornings attempt to rescue shares from the cache pool (moved moved system to the array, well it moved 75% of it the rest was corrupted so badly it would put the pool in read mode when I tried to move them).
I'm not actually going back to an image, I only wanted to try it to see if it was any different.
I also had totaly nuked the docker directory before posting both via the gui and a good old rm -rf when the gui failed to do it.
SOLUTION: On the plus side I have actually resolved this with the single worst tool everyone has in their toolbox. A system restart (the first one since formating the pool and nuking the docker directories).
I have now been able to re-create the docker directory and get my apps back. Thanks for the help anyway. I will mark the subject as solved.
