November 24, 2020, 6:54pm
As of today I stuck at 1.5.3 version for two weeks, but
v1.17.4 is already released.
I`m getting the latest version of the storagenode as it said in
the documentation, like this:
docker pull storjlabs/storagenode:latest
Is it ok?
May be this is the reason I don`t get any usage traffic anymore?
My node’s stats can be found here.
I update manually
Why do you prefer that over automatic update ?
November 24, 2020, 7:05pm
After trying to pull the new image, did it tell you no new image was found? If you update manually, I am assuming you know to rm and re-create the container after a new image pull.
November 24, 2020, 7:10pm
Well… Ok… I didn`t know I have to recreate the container.
konard@konard-desktop:~$ sudo docker stop storagenode
[sudo] password for konard:
konard@konard-desktop:~$ sudo docker rm storagenode
konard@konard-desktop:~$ sudo docker pull storjlabs/storagenode:latest
latest: Pulling from storjlabs/storagenode
Status: Image is up to date for storjlabs/storagenode:latest
konard@konard-desktop:~$ sudo docker run -d --restart unless-stopped --stop-timeout 300 -p 28967:28967 -p 192.168.1.74:14002:14002 -e WALLET="0x102c4f1957484E3cf5507B115cFa9fB47da7862A" -e EMAIL="email@example.com" -e ADDRESS="konard.ddns.net:28967" -e STORAGE="1750GB" --mount type=bind,source="/mnt/usb-Seagate_BUP_Slim_BL_NA7LAG1K-0:0-part1/identity/storagenode",destination=/app/identity --mount type=bind,source="/mnt/usb-Seagate_BUP_Slim_BL_NA7LAG1K-0:0-part1/storj/storj",destination=/app/config --name storagenode storjlabs/storagenode:latest
I executed these commands and it updated to v1.16.1, but not v1.17.4.
November 24, 2020, 7:14pm
My answer didn`t pass the spam filter, here is the image:
November 24, 2020, 7:15pm
The image for 1.17.4 won’t be released to docker until the rollout is complete for Windows GUI and Linux native updater. Usually about a week after the change log is posted.
I see your reply in the previous post, no issues.
November 24, 2020, 7:19pm
No reason, now I’ll try the automatic update.
Great. This post might help motivate others too.
Hello Storage Node Operators!!
We’ve got some important changes to the Storage Node Software and the network and it’s important that all of our SNOs are aware of and understand these changes.
First, it’s vitally important that your storage node software automatically updates. If you have installed your storage node through
our official instructions (either via our Windows installer or official Docker instructions using Watchtower), you have nothing to worry about and your node will automatical…
November 25, 2020, 11:26am
Does it mean I’ve been disqualified already?
curl -s https://version.storj.io 10 | jq .processes.storagenode.minimum.version
"1.16.1" today, but I had 1.5.3 for two weeks…
November 25, 2020, 2:17pm
I am not sure if DQ for old versions is live yet (everyone should assume it is), but in a nutshell:
1 minor version behind = okay
2 minor versions behind = no ingress
3 minor versions behind = DQ’d
So if you were running 1.15.3 and version 1.17.4 was just released, you would be two minor versions behind at most. So your node should be fine.
November 25, 2020, 5:06pm
any idea how often are the version release?
i need to run manual updates as well…
November 25, 2020, 6:34pm
There is no set schedule. The best you can do is either subscribe to notifications for new posts in
Engineering Discussions, as changelogs are posted there, or Watch the Github repository and set up notifications for new releases. Version info is also available via https://version.storj.io by looking at the
processes:storagenode values for
minimum (1 minor release behind) and
suggested (current release) versions.
November 25, 2020, 7:02pm
I use diun to watch my docker containers. Not ideal as diun requires root access to docker too…
November 26, 2020, 2:39am
i use podman, so now i facing problem because podman doesnt have daemon…
maybe i should go back docker haha
docker run -d --restart=always --name watchtower
-v /var/run/docker.sock:/var/run/docker.sock storjlabs/watchtower storagenode watchtower --stop-timeout 300s