TL;DR: The Storj Node Docker image is being updated to store binaries on the host system. This requires executable permissions on the host path that is mounted to /app/config directory. If you have a restrictive filesystem, you may need to adjust permissions. You can set a custom path with BINARY_…

I think we would not change the way of communication. [image] Spawnerr: no permission to run command I do not think that there something regarding changing of the communications channel in the roadmap. There is also a problem with mass email relays - most will add satellites or address which we …

These changes that potentialy affect in a bad way the node functionality should be optional, not forced imposed on good old working nodes. Many don’t keep an eye on the nodes or their percormance, don’t reed the forum, and expect the nodes to work, once set up and tuned to their particular enviromen…

Thank you for your valuable feedback. I apologise for the inconvenience caused by the short notice. Before rolling out this change, there were several factors that were considered: This change fixes a very critical issue This is basically a change that majority of SNOs have to do nothing. We sto…

[image] Scriptiee: and now I’m actually running it as pods in k8s Now it could explain to me, why you were need more time for testing. How do you mount a storage there?

Hi, i would notify to all that i have update the docker on UNRAID and it upgrade of the docker is normally and perfectly. I use the standard configuration for the path and the docker is updates automatically

Can it be the reason for this? All of a sudden I am getting the same error: [image] Storagenode stopped working on Pi4 - ERROR: The certificate of 'version.storj.io' is not trusted troubleshooting Hi, my storagenode is not working anymore. Probably it happened after auto…

It could be possible, because the image should also got updates for the underlying OS. However, I tested this new image for ARM64 and it didn’t have this issue. This is usually happen, if a ca-certificates package is not updated. The OS is updated by the way: Dockerfile: upgrade distro buster to …

[image] Scriptiee: Anyway, I appreciate you at least acknowledging that this is indeed an inconvenience, and not jump on the ship of “well it’s your fault” like some replies I received. I too believe it’s completely and entirely your fault, and the purpose of these comments is not to jump on …

I think we could do a change to affect less non-default setups, if we would download to /app/config/bin if there are no binaries, but then copy them to some folder inside the container, which is not exposed to the host and where we can set proper permissions, like /app/bin and use it to run binaries…

Just to let you know, I have a Qnap arm, the TS230, and the container upgrade went smoothly

Storagenode Docker Update: Changes To Binaries Location For Persistence Between Restarts

Node Operators

jammerdan September 22, 2024, 12:40pm 31

Can it be the reason for this? All of a sudden I am getting the same error: