with reading the official docs and a lot in this community I was able to set up two containers on my Synology.
As I have to update these now, I got questions.
In the docs they write we have to mount the data and identity folders with fstab on linux.
So I guess I need to do this on my Synology this way, but fstab is not available there, so I didn’t.
So I have mounted it with it, can I assume that I can normally shutdown the container / Synology for updates and everything starts again with the mounts?
And also can I just use watchtower with this and everything is fine?
I think the Synology Nas handles that for you, just verify it with a reboot if the Storage is on the same mountpoint as before (/volume1/ and the other disk on USB).
Yes, as long as docker gets also started automatically as a Service (which i assume on Synology) all containers will also be started. Thats because of this Flag (which is a RestartPolicy, see Start containers automatically | Docker Docs): --restart unless-stopped
To be 100% sure test it with a reboot of your NAS
As long as you configure it as in the Documentation yes, i never had any issues with it. But to be sure i would recommend to verify it on a monthly basis.
Also i would recommend an external Monitoring tool (like uptimerobot), so you get alerted in case something goes wrong. Also you might want to have a fancy Dashboard with Historical Graphs, check this Guide out:
But as it will delete the existing container if an update exists, I wonder how watchtower knows the paths to data and identity for the new, updated container?
I am not 100% sure but i assume it will read the config of the running container (you can do it with docker inspect → docker inspect | Docker Docs), copy it and apply it to the new one.
Official Documentation:
Watchtower will pull down your new image, gracefully shut down your existing container and restart it with the same options that were used when it was deployed initially.