Is your issue resolved ?
1 Like
root@vmd43569:~# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
storjlabs/watchtower latest 84803293c0e3 7 months ago 14.5MB
A lot of members wrotes a lot of commands… I have used: “docker system prune -a” and deleted 466.5 MB, but the image id is still wrong. How can i fix it?
Can you please elaborate ?
Stop, remove, and update watchtower:
docker stop -t 300 watchtower
docker rm watchtower
docker pull storjlabs/watchtower
docker run -d --restart=always --name watchtower -v /var/run/docker.sock:/var/run/docker.sock storjlabs/watchtower storagenode watchtower --stop-timeout 300s
docker image prune
Verify watchtower running
docker ps
Verify watchtower image id is 6af6621e20c1
docker images
3 Likes
The new version will ignore the --interval flag
Removed unused option in my above post.
1 Like
yes, thank you. Used the -a flag you posted above.
1 Like
if you have issues with respawning multiple instances of watchtower, you can kill them all (powershell/bash):
docker rm --force $(docker ps -qf ancestor=storjlabs/watchtower)
and run only one instance
1 Like
I have 4 storagenodes on the same server and never had a single problem with watchtower updating all of them.
People who don’t have problems usually don’t complain in the forum 
2 Likes
For Raspberry Pi the correct Watchtower version is:
Latest or Latest-arm32v6?
It should be :latest. The manifest should be detected automatically.
1 Like
Thank you, but looks like it is already updated it self:
latest: Pulling from storjlabs/watchtower
Digest: sha256:31c0c558ec8adad5cec6cb86320c58018289ca22dafa019c31cd5d6f65f03655
Status: Image is up to date for storjlabs/watchtower:latest
docker.io/storjlabs/watchtower:latest
1 Like
docker stop -t 300 (copy name of the container)
docker rm (copy name of container)
Check if its removed
docker ps -a
Also you can check if there are any other unused images by
docker images -a
Looks like it ghost 
docker stop -t 300 _HqSJvRxicmKQivLbvHw
Error response from daemon: No such container: _HqSJvRxicmKQivLbvHw
docker images -a
REPOSITORY TAG IMAGE ID CREATED SIZE
storjlabs/storagenode beta 927cebfc3923 7 days ago 28.2MB
storjlabs/watchtower latest 6af6621e20c1 3 months ago 14.3MB
storjlabs/watchtower 84803293c0e3 7 months ago 14.5MB
Try this and answer Y when prompted
docker system prune -a
Thank you. Did not worked out. Ghost container still runs. Also i have checked another my node, there is the same story 
Total reclaimed space: 0B
Same 3rd container, just the letters in the naming different.
> docker rm container <container-id> -f
2 Likes
Maybe a dumb question, but is it a problem to run the manual update command, while the (autoupdate) watchtower container is running?
There is no such thing as dumb question. Its not a problem for watchtower to be running. Also you shouldn’t force manual update if watchtower is running smoothly.