Hi @bovcan
Your hint guided me to search the “error” in the “docker-universe” as QNAP is not more the only intersection.
Both of my Storagenode are now up and running. I just added " --privileged " to the run-command.
Seems really a permission issue. Strange is here that it seem to happen only after upgrade to actual version without touching any docker/qnap-components.
I also tested if the storagenode is running after migration to DB43 without --privileged. => No!