Please, update your watchtower command as soon as possible

Node Operators
1
  1. Stop the watchtower: docker stop watchtower
  2. Remove the watchtower: docker rm watchtower
  3. Run the watchtower:
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

It should prevent the whole network down on the update

8 Likes
3

small correction:

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

removed s

4 Likes
4

For ARM based platforms like Odroid N2, use this command:
docker run -d --restart=always --name watchtower -v /var/run/docker.sock:/var/run/docker.sock storjlabs/watchtower:latest-arm32v6 storagenode watchtower --stop-timeout 300s --interval 21600

3 Likes
5

My node upgraded properly before I was able to update the watchtower command.

6

what is this used for i have the whole command same expect for this ? do i still need to update? my updates are working fine till now…i am on 19.5 now

7

It’s used to spread out when nodes are updating to help prevent many nodes running into issues at the same time as a result of an update. Yes you should still change it.

8

Thanks @Alexey,
It looks like I was still running the original watchtower from the docs where it didn’t have

--stop-timeout 300s

I have removed and updated my watchtower options now :+1:

1 Like
9

Hi.
I am using a Rock64 machine which is a 64bit system. Should I just replace the 32 in this command with 64, or is there a different command for 64 bit Ubuntu machines?
Thanks.
Ilan

10

I tried and got this error:
image

Also when I check my system I show I have an ARMv7.
Does that matter?

image
image660Ă—777 17.9 KB

11

Please, try to use just a latest tag

12

Like this?
image

13

Exactly. Is it working?

docker ps
14

Yes appears so. Up 7 Mins.
Thanks!

1 Like
15

This still does not work for me.

image
image1088Ă—69 11 KB

As you can see from teh image, watchtower has been running for 2 weeks. However, I had to manually update my storagenode beta manually 6 days ago.

16

Please, wait for tomorrow and check again.
Also, please, give me logs from the watchtower:

docker logs watchtower
17

Interesting looks like it has done nothing since it was started:

storj@pine64 : ~ $ docker logs watchtower
time=“2019-09-30T21:42:47Z” level=info msg=“Unable to update container /watchtower. Proceeding to next.”
time=“2019-10-01T21:42:48Z” level=info msg=“Unable to update container /watchtower. Proceeding to next.”
time=“2019-10-01T21:42:53Z” level=info msg=“Unable to update container /storagenode. Proceeding to next.”

18

Try to remove the watchtower and run it again:

docker stop watchtower
docker rm watchtower

Then run it back: https://documentation.storj.io/setup/cli/software-updates#automatic-updates

19

Thx, @Alexey

Anyway, yes, I did the stop/rm and rerun after my earlier post. It’s been running for 9hrs now but there is nothing in the logs. Should there be some indication in the log that it did something since it should be checking for new versions every 6hrs?

20

no, only if it found a new image:

time="2019-10-16T18:10:08Z" level=info msg="Found new storjlabs/storagenode:beta image (sha256:694739e41afd626821a7747c9a74259b6d6000a71baa37767fbfe2ae3e1c33ef)"
time="2019-10-16T18:10:10Z" level=info msg="Stopping /storagenode (b889b2c723c7815fb14c3ca638c2d14e6a6fd17e6dfa11284b20dc4caafcf71d) with SIGTERM"
time="2019-10-16T18:10:13Z" level=info msg="Creating /storagenode"