Synology DSM updates that work with Storj

Node Operators
,
1

I will post here every DSM and CM update that I install and check for working with storagenodes.
I run DS216+ 1GB and DS220+ 18GB, 1 or 2 drives, ext4 FS, no RAID, no SSD cache.

27.06.2023

  • DSM 7.2-64570 Update 1: GOOD.
  • Container Manager 20.10.23-1413: GOOD.
    Docker is auto-replaced with Container Manager, by Docker Inc.
    No SN stop needed for update.
3 Likes
2

Storagenode runs in a container, to isolate it from the host. Are you suspecting Synology will break docker in one of the updates?

1 Like
3

I hope not, but BS told me in an older post that a Docker update, if I recall corectly, crashed some nodes…
I hope all works well with every update, but just to assure everyone, who is hesitant with new updates, that all is fine (or not :grimacing:), I will try to keep this post up-to-date. I set autoupdate on for DSM and packages, with no notifications, so maybe I will miss some; but I’ll try to check from time to time the installed versions.

2 Likes
4

It definitely broke things once before. Though it’s a long time ago now and I don’t remember the exact details. But I had been holding off on DSM 7.2 for this reason as I knew they were making some significant changes to docker. So I appreciate your post!

2 Likes
5

The newest DSM version 7.3.2-86009 requires updating the Container manager also (to ver. 24.0.2-1606), if isn’t up-to-date, and manual restart of containers after DSM update.
The watchtower started by itself, but the storagenodes didn’t, so, for example, if you have 2 nodes:

docker restart -t 300 watchtower

docker restart -t 300 storagenode

docker restart -t 300 storagenode2

I keep all packages up-to-date by default, by setting “install all updates”. I didn’t have problems with them. I also keep DSM autoinstall on. I believe this last DSM update requires manual intervention, because you must aknowledge that packages require updates and containers restart, so it dosen’t start by itself.