Good point, yes, this could be the initial root cause. But still I do not understand the error messages, as the files itself are there (maybe corrupt?). But yes, the Node may have these legacy issues for a minority.
Valid point. I’ll extend that by the docker stop command - and changed it anyway to get executed, when one of the issues occurred, which were described in the post - not on a daily base. Nevertheless, that was not fired since then, but could explain issues with single files.