Yes, but you may specify it like -e STORAGE="" (literally empty), then it should take the value for allocation from the config.
2 Likes
Ou, I see. I thought you meant in the config. I’ll try it. Thanks!
1 Like
Ohhh Thank’s Alexey !!! 
It’s a bit tricky, fortunately I came across your message, because I tried to solve with chatgpt but it’s real Boulshit that returned me 
It would be nice if we could pin discussions that are really useful in the forum.
Is there any reason that it won’t be supported by default if it’s empty?
I have another question but maybe I should make a new tread.
So it works fine with the yaml config but I set the value to 14.75 TB and my node sets it to 13.71TB, is this a setting to respect 10% empty space that is applied by default?
no. The node checks the available space on start. Seems your disk has only 13.71TB available space (if you mean the Total Disk Space value on the donut chart), including used space by the node. It may helps to enable scan on startup, if you disabled it and restart the node to allow it to recalculate the used space.
Or you mixed different measure units. Our software uses SI measure units, but most of OSes uses binary measure units, so 14.75 TB is 13.41 TiB.