Updating Storage Node’s Available Space?

[Roberto]

The docker command takes priority over the config file. You must stop the node, remove it and reissue the command to create the node with the new command

docker run -d --restart unless-stopped --stop-timeout 300
-p 28967:28967/tcp
-p 28967:28967/udp
-p 14002:14002
-e WALLET=“xxx”
-e EMAIL=“xxx”
-e ADDRESS=“wan_ip:28967”
-e STORAGE=“20TB”
–mount type=bind,source=“/volume1/Storj/Identity/storagenode/”,destination=/app/identity
–mount type=bind,source=“/volume1/Storj/”,destination=/app/config
–name storagenode storjlabs/storagenode:latest
–log.level=error

Questions and sugestions about config.yaml

I’m running storagenodes on NAS (linux) in Docker. After starting a few nodes in different months, I see that the parameters in config.yaml had changed over time with newer releases. Some new appeared, some disappeared, some changed the default values. But the config file dosen’t change with stortagenode update. I imagine that storagenode uses the default values for new parameters, even if they are not present in config file. But what if someone needs/wants to change something, and has and old…