Hello @arumes31 ,
Welcome to the forum!
This is likely wouldn’t help, the only affecting change could be the image above. And I suspect the issue that the drive on QNAP is mounted with noexec.
The base image doesn’t contain neither storagenode nor storagenode-updater, it has only a downloader and supervisor. Then it run storagenode-updater and storagenode, then storagenode-updater will download a new version of storagenode and itself, updates them and restart. So the node will be updated again, if it’s eligible to be updated.
The simplest solution would be to use a docker image and mount it to /app/config/bin in the container. You may add this option to your docker run command before the image name:
...
-v storagenode-binaries:/app/config/bin \
...
storjlabs/storagenode:latest