Changelog v0.29.3

Which command did you use to start watchtower?

this from documentation

docker run -d --restart=always --name watchtower -v /var/run/docker.sock:/var/run/docker.sock storjlabs/watchtower storagenode watchtower --stop-timeout 300s --interval 21600

C:\Users\Mihal>docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4d525f4c16cf storjlabs/watchtower “/watchtower storage…” 6 minutes ago Up 6 minutes watchtower
5caab343a425 storjlabs/storagenode:beta “/entrypoint” About an hour ago Up 24 minutes 127.0.0.1:14003->14003/tcp, 0.0.0.0:28966->28967/tcp storagenode_1
cee2fe9ed6a1 storjlabs/storagenode:beta “/entrypoint” 11 days ago Up 24 minutes 127.0.0.1:14002->14002/tcp, 0.0.0.0:28967->28967/tcp storagenode

okey right after my last reply it updated

Ok I ran into the same kinda issue with mine some reason watchtower doesnt like to update 2 storagenodes, I had to update them manually

Do you mean that you have run both nodes on the same PC?
if so, you should add both names to the watchtower command

I also did that,
docker run -d --restart=always --name watchtower -v /var/run/docker.sock:/var/run/docker.sock storjlabs/watchtower storagenode storagenode2 watchtower --stop-timeout 300s --interval 21600

Never updated both of them. I waited 2 days after the update to see if they would but they didnt.

I have 4 nodes on the same server and watchtower updates all of them. Make sure you put the right names of your nodes in the watchtower command. Compare the names with the output of docker ps.

Yeah I triple checked everything, Im gonna see next update it may have been a dns issue not 100% sure.