I did edit container and changed the STORAGE environment to the new size (larger).
After restarting I went to the volume containing the config.yaml. The configuration change is reflected there!
When I go to the Sorj Node Dashboard it’s still displaying the old “Total Disk Space”. Unfortunately the logs aren’t displaying the loaded values at startup (enhancement perhaps?).
Am I not patient enough or is there something else i have to do?
I would recommend to do not use GUI to operate docker containers, because you do not control how authors implemented their wrapper around the docker. Something can be broken or can even lead to disqualification (like it were with using of -v option instead of --mount, see Node disqualified...WHY? - #10 by BrightSilence)
After updating the STORAGE environment you need to re-create the container, to do so you need to stop and remove the container and create a new one with all your parameters include changed ones.
In CLI it’s easy to do
There is a bug in Portainer that it can’t update some settings on a Synology Docker installation… You can guess it… Environment variables is one of them.
When I changed the environment variable through the Docker application in Synology OS. It worked directly as expected.