If that true why recommend what you recommend? You even test yourself?
Because this is a forum not the official Synology Knowledge Base, and as such, it is filled with experimental fixes and solutions. Everything here comes with the implied "do at your own risk". Yes, I'm using it and it's working as expected - updating all my containers and retaining my settings. I recommended it for people who'd find it useful as I did. And lo and behold it was useful for some one at least ... see below! In the end no one forced you to do it. So you can either not use it or provide another solution but your incessant crying about it just wastes everyone's time. Stop being a troll.
Nice find! Will try that out.*mightbetrue wrote:
<update>webhippie/watchtower is like 2 month old and can be convinced to use server api version 1.23:
docker run -d -e DOCKER_API_VERSION="1.23" -v /volume1/docker/docker.sock:/var/run/docker.sock webhippie/watchtower
Hint: /volume1/docker/docker.sock is a symlink to /var/run/docker.sock.
Actually it does do the trick! Now also the env variables are preserved. safely updated all my linuxserver.io containers to the latest image.
*Although, centurylink/watchtower was preserving env's for me. The only thing it wasn't remembering was the website you can point the shortcut to. But I can just re-add that in, so not a big issue. But I will try your suggested version out nonetheless.
PS. don't bother with him/her, he/she is ungrateful and will give you non stop complaints.
PSS. As far as v2tec using a newer API, they have been made aware of it not working on Synology via an open GitHub issue and it's in their version 2.0 to do list to lower their API requirements.
PSS. You sure it's webhippie/watchtower and not allmende/watchtower? It seems allmende posted those changes in a pull request but webhippie hasn't commited them yet...
Update: It's not working with allmende/watchtower (logs are throwing errors), so it must be webhippie/watchtower.