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

[Alexey]

I think we would not change the way of communication.

@Alexey

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 could use as a spammer and we cannot communicate important things to our customers. So, I would not expect that something would change here.
So, I can only suggest to subscribe to the forum.

Maybe only to add an active notifications to the storagenode dashboard, but it is not in a roadmap too. They are almost static or provided by the node itself (like a DQ message or a Suspension message).

@Scriptiee

Does falling back to older version is a feasible workaround for the time being until one figures out how to resolve this on their setup?

no, it’s not. But you may change the binary location in multiple ways:

@clement

You can set a custom path with BINARY_DIR environment variable. Default is /app/config/bin

You may also mount this location from a different drive or even a docker volume. The last one would also solve any permissions issues, I believe.