No ingress in the last 16 hours

[RuMbOiDe]

Hi there,

I’ve got a node in docker linux arm32 (RPi4B) using the tag “latest”, so my version is 1.49.5.
16 hours ago I dont receive ingress, egress works perfectly.

Am I forced to update my node manually to have ingress? I prefer still using “latest”.

Thanks in advance.
Regards.

[gs.gs]

Same here
Also on RPI. what should we do?

[baker]

@RuMbOiDe and @gs.gs At the moment, the latest tag will not update for for arm32. You will need to manually update your nodes with a specific image, otherwise your nodes will not get any more ingress. I know Storj is working on updating the latest tag, but for now you will have to use a specific tag.

Stop your node, remove the container, and run your docker run command again, except instead of using storjlabs/storagenode:latest change the image to

storjlabs/storagenode:bfc3d4c9d-v1.52.2-go1.17.5

More info can be found here:

Changelog v1.52.2

The changelog for v1.51.2: Release v1.51.2 · storj/storj · GitHub The changelog for v1.52.2: Release v1.52.2 · storj/storj · GitHub For docker nodes Like last time we would like the docker nodes to test out the new image early (bfc3d4c9d-v1.52.2-go1.17.5). The reason for this is that we switched to a different base image. That should fix most of the bugs we have seen last time. We are especially interested in arm32 nodes but also all other architectures.

And keep an eye on that forum category to see when you can switch back to the latest tag. This version downloads the updater inside the container, so it should be able to keep your nodes current for the time being.

[RuMbOiDe]

Thanks @baker !!!
It works! But the image is storjlabs/storagenode:bfc3d4c9d-v1.52.2-go1.17.5

Greetings!

[baker]

Glad it worked! And thanks, I fixed the storjlabs part of the image in my post. I am constantly making that mistake, good catch!

[gs.gs]

Thanks @baker, I’m back in business!

[MarP]

So what’s the point of having watchtower (the storj edition) taking care about node updates if it will end up not working properly?

[Alexey]

It’s working. Just latest tag was not updated to have arm32. This is for the reason:

@littleskunk

For docker nodes
Like last time we would like the docker nodes to test out the new image early ( bfc3d4c9d-v1.52.2-go1.17.5 ). The reason for this is that we switched to a different base image. That should fix most of the bugs we have seen last time. We are especially interested in arm32 nodes but also all other architectures.

The previous base image for arm32 (official alpine) has a lot of bugs, which prevented to work normally almost all arm32 nodes without patch of the underlaying OS (!). So we decided to do not push the latest tag for arm32 until it will be fixed and tested by the Community.
When all concerned SNO with arm32 have tested it and have not had issues (mostly) - it was updated.
Now the watchtower will update your arm32 node within 24-72 hours after the push.