I believe that watchtower initiated the update, thus it loaded watchtower and storagenode images, then it noticed the update in the storagenode image and killed the container and started another one.
Our storagenode image contain only downloader, so it downloaded the same 1.52.2 storagenode binary and restarted it, did the same for storagenode-updater binary and restarted it too.
Then both processes remain working and checking for when your node would be eligible for the next version to update.
The last part from the logs is related to this issue: Processes entered FATAL state, too many start retries too quickly and it’s not prevent storagenode from running as far as I know.
Please confirm, that your storagenode is running and you did not start it manually.