Changelog v1.52.2

If you created it inside the container - it has been flushed away with removing of the container.

Well, I removed the container:

sudo docker stop -t 600 "storj_node_2"
sudo docker rm "storj_node_2"

Then pulled the new image with:

sudo docker pull storjlabs/storagenode:latest

Then I started the node again with my full command:

sudo docker run -d --restart unless-stopped \
    [... many stuff such as ports, wallet address, email ...]
    --name "storj_node_2" \
    storjlabs/storagenode:latest \
   [... other stuff such as zksync ...]

So, do you confirm the latest ARM32 image is fixed with regards to the missing supervisor folder? How could both images have the same ID then? :thinking:

I do not have arm32 anymore, so cannot confirm, sorry.

Alright that’s fine, no worries :slight_smile:
It works fine now on my end, so all is good :+1:

1 Like

The CRITICAL logs are safe to ignore for now. See my response here: [Tech Preview] Storagenode Updater inside Docker - #33 by clement and [Tech Preview] Storagenode Updater inside Docker - #32 by clement

However, we have PRs ready to get rid of the CRITICAL error logs:
https://review.dev.storj.io/c/storj/storj/+/7332
https://review.dev.storj.io/c/storj/storj/+/7341
https://review.dev.storj.io/c/storj/storj/+/7342

2 Likes

Thank you! Watchtower updated my nodes, they’re all updated to 1.52.2 and ingress has resumed.

I am still going to look at updating to 64bit OS. These nodes are too much like pets, need to make them cattle. Then I won’t be afraid of updating them.

3 Likes

Ok, so when I move a 1.52. node now to a HC2 it should not create any problems starting it with the latest tag?

It should update normally. However, I have not saw reports from HC2 owners regarding this latest image. Probably they are just works, so there is nothing to report.

I’ll try and report back. Hopefully everything will work.

3 Likes

Seems to be working. Node up and running since a few minutes ago. So far no problems.

2 Likes

I changed mine back to latest and ended up with zero ingress when I checked a couple hours later. Set it back again and it’s working on Pi4

If you do not have watchtower, then you need to pull the latest and then run with latest tag.
If you have a watchtower - it checks for updates at random interval between 12 and 72 hours.

1 Like

Yes, it just works. Just pulled the latest tag, actually it’s the same image of the one I was using on my HC2 as suggested in this thread, so I’m reverting back to the latest tag:

I’ve also noticed my node upgraded to v1.53.1.

Many thanks to the Storj team for their endeavour to continue supporting 32 bit ARM boards. With 8 cores, 2GB RAM and native SATA interface I think the HC2 board, although based on an old chip, is up to the job if paired with a CMR disk (my node is running on a Seagate IronWolf 8TB)

2 Likes

For honestly I like this board too. I do not have it in my farm, but it look pretty nice and simple.

1 Like