# Any updates for storjlabs/storagenode:latest docker?

**URL:** <https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401>\
**Category:** troubleshooting\
**Created:** [November 24, 2020, 6:54pm UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401 "2020-11-24T18:54:48Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Konard](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/konard/32/63_2.png) [@Konard](https://forum.storj.io/u/Konard)\
**Post date:** [November 24, 2020, 6:54pm UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401/1 "2020-11-24T18:54:48Z")

</div>

[![image](https://lc-storj.ams3.digitaloceanspaces.com/original/2X/0/0c1b06893c6ee31be5f6c4db5628d7e4141a9e74.png)](https://hub.docker.com/r/storjlabs/storagenode/tags?page=1&ordering=last_updated&name=latest)

As of today I stuck at 1.5.3 version for two weeks, but [v1.17.4](https://github.com/storj/storj/releases/tag/v1.17.4) is already released.

[![image](https://lc-storj.ams3.digitaloceanspaces.com/original/2X/f/febfed37047bf0465e579c46df20b3f00c374464.png)](http://konard.ddns.net:14002/)

I`m getting the latest version of the storagenode as it said in [the documentation](https://documentation.storj.io/setup/cli/storage-node), like this:

```auto
docker pull storjlabs/storagenode:latest

```

Is it ok?

May be this is the reason I don`t get any usage traffic anymore?

P.S.  
My node’s stats can be found [here](http://konard.ddns.net:14002/).

---

<div class="post-metadata">

**Author:** ![nerdatwork](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/nerdatwork/32/1135_2.png) [@nerdatwork](https://forum.storj.io/u/nerdatwork)\
**Post date:** [November 24, 2020, 7:03pm UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401/2 "2020-11-24T19:03:38Z")

</div>

Do you have watchtower ?

---

<div class="post-metadata">

**Author:** ![Konard](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/konard/32/63_2.png) [@Konard](https://forum.storj.io/u/Konard)\
**Post date:** [November 24, 2020, 7:03pm UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401/3 "2020-11-24T19:03:58Z")

</div>

No, I update manually.

---

<div class="post-metadata">

**Author:** ![nerdatwork](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/nerdatwork/32/1135_2.png) [@nerdatwork](https://forum.storj.io/u/nerdatwork)\
**Post date:** [November 24, 2020, 7:05pm UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401/4 "2020-11-24T19:05:00Z")

</div>

> [@Konard](#):
>
> I update manually

Why do you prefer that over automatic update ?

---

<div class="post-metadata">

**Author:** ![baker](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/baker/32/6110_2.png) [@baker](https://forum.storj.io/u/baker)\
**Post date:** [November 24, 2020, 7:05pm UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401/5 "2020-11-24T19:05:37Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Konard](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/konard/32/63_2.png) [@Konard](https://forum.storj.io/u/Konard)\
**Post date:** [November 24, 2020, 7:10pm UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401/6 "2020-11-24T19:10:54Z")

</div>

Well… Ok… I didn`t know I have to recreate the container.

```auto
konard@konard-desktop:~$ sudo docker stop storagenode
[sudo] password for konard: 
storagenode
konard@konard-desktop:~$ sudo docker rm storagenode
storagenode
konard@konard-desktop:~$ sudo docker pull storjlabs/storagenode:latest
latest: Pulling from storjlabs/storagenode
Digest: sha256:1378b23f8097ed8dc5709af40fff47828521cf5d7409c9fca20df78747e99a6f
Status: Image is up to date for storjlabs/storagenode:latest
docker.io/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="drakonard@gmail.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
d69a9a5bef973c028c609e77f1f2bea59823fad70e091d5dee86fa81f7fd2967

```

I executed these commands and it updated to v1.16.1, but not v1.17.4.

---

<div class="post-metadata">

**Author:** ![Konard](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/konard/32/63_2.png) [@Konard](https://forum.storj.io/u/Konard)\
**Post date:** [November 24, 2020, 7:14pm UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401/7 "2020-11-24T19:14:10Z")

</div>

My answer didn`t pass the spam filter, here is the image:

 ![image](https://storj-s3.bcdn.literatehosting.net/original/2X/0/04d314eea3fee891fcecfb110d172a787a60fb92.png)

---

<div class="post-metadata">

**Author:** ![baker](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/baker/32/6110_2.png) [@baker](https://forum.storj.io/u/baker)\
**Post date:** [November 24, 2020, 7:15pm UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401/8 "2020-11-24T19:15:35Z")

</div>

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.

> [@Konard](#):
>
> My answer didn`t pass the spam filter, here is the image:

I see your reply in the previous post, no issues.

---

<div class="post-metadata">

**Author:** ![Konard](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/konard/32/63_2.png) [@Konard](https://forum.storj.io/u/Konard)\
**Post date:** [November 24, 2020, 7:19pm UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401/9 "2020-11-24T19:19:14Z")

</div>

No reason, now I’ll try the automatic update.

---

<div class="post-metadata">

**Author:** ![nerdatwork](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/nerdatwork/32/1135_2.png) [@nerdatwork](https://forum.storj.io/u/nerdatwork)\
**Post date:** [November 24, 2020, 7:46pm UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401/10 "2020-11-24T19:46:04Z")

</div>

> [@Konard](#):
>
> now I’ll try the automatic update

Great. This post might help motivate others too.

> [@Keeping your node up to date, changes to storage node software! PLEASE READ this thread!](https://forum.storj.io/t/keeping-your-node-up-to-date-changes-to-storage-node-software-please-read-this-thread/9722):
>
> 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](https://documentation.storj.io/setup/cli/software-updates) (either via our Windows installer or official Docker instructions using Watchtower), you have nothing to worry about and your node will automatical…

---

<div class="post-metadata">

**Author:** ![Konard](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/konard/32/63_2.png) [@Konard](https://forum.storj.io/u/Konard)\
**Post date:** [November 25, 2020, 11:26am UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401/11 "2020-11-25T11:26:21Z")

</div>

Does it mean I’ve been disqualified already?

```auto
curl -s https://version.storj.io 10 | jq .processes.storagenode.minimum.version

```

Gives `"1.16.1"` today, but I had 1.5.3 for two weeks…

---

<div class="post-metadata">

**Author:** ![baker](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/baker/32/6110_2.png) [@baker](https://forum.storj.io/u/baker)\
**Post date:** [November 25, 2020, 2:17pm UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401/12 "2020-11-25T14:17:44Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![zethsqx](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/zethsqx/32/1131_2.png) [@zethsqx](https://forum.storj.io/u/zethsqx)\
**Post date:** [November 25, 2020, 5:06pm UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401/13 "2020-11-25T17:06:11Z")

</div>

any idea how often are the version release?  
i need to run manual updates as well… 😐

---

<div class="post-metadata">

**Author:** ![baker](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/baker/32/6110_2.png) [@baker](https://forum.storj.io/u/baker)\
**Post date:** [November 25, 2020, 6:34pm UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401/14 "2020-11-25T18:34:15Z")

</div>

There is no set schedule. The best you can do is either subscribe to notifications for new posts in [Engineering Discussions](https://forum.storj.io/c/engineer-amas/27), as changelogs are posted there, or Watch the [Github repository](https://github.com/storj/storj/releases) and set up notifications for new releases. Version info is also available via [https://version.storj.io](https://version.storj.io) by looking at the `processes:storagenode` values for `minimum` (1 minor release behind) and `suggested` (current release) versions.

---

<div class="post-metadata">

**Author:** ![kevink](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kevink/32/6077_2.png) [@kevink](https://forum.storj.io/u/kevink)\
**Post date:** [November 25, 2020, 7:02pm UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401/15 "2020-11-25T19:02:39Z")

</div>

I use diun to watch my docker containers. Not ideal as diun requires root access to docker too…

---

<div class="post-metadata">

**Author:** ![zethsqx](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/zethsqx/32/1131_2.png) [@zethsqx](https://forum.storj.io/u/zethsqx)\
**Post date:** [November 26, 2020, 2:39am UTC](https://forum.storj.io/t/any-updates-for-storjlabs-storagenode-latest-docker/10401/16 "2020-11-26T02:39:37Z")

</div>

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
