Allocated disk space issue

Tempest · April 23, 2026, 3:25am

Just updated to 152.5 however now i’m in a way overused disk situation. Its not listening to my disk allocated parameter even after I recreated the container and never touched the config file.

Available Used Egress Ingress
Bandwidth N/A 2.33 TB 0.96 TB 1.37 TB (since Apr 1)
Disk 0 B 7.70 TB

df -h
/dev/sda1 15T 11T 4.1T 73% /mnt/exos16tb

from config.yaml
storage.allocated-disk-space: 13.00 TB

Alexey · April 23, 2026, 4:33am

If you use a docker version, you must not touch the allocation in the config.yaml, it will be ignored. You need to use the -e STORAGE=13TB parameter instead in your docker run command (before the image name), see

If -e STORAGE= is not specified, it will use 2TB by default:

github.com/storj/storagenode-docker

Dockerfile

a187f986c


      
          
          EXPOSE 28967
          EXPOSE 14002
          
          WORKDIR /app
          ENTRYPOINT ["/entrypoint"]
          
          ENV ADDRESS="" \
              EMAIL="" \
              WALLET="" \
              STORAGE="2.0TB" \
              SETUP="false" \
              AUTO_UPDATE="true" \
              LOG_LEVEL="" \
              BINARY_STORE_DIR="/app/config/bin"

Awful_Charlie · April 23, 2026, 6:20am

Is there a change to the behaviour post 1.148.3?
I have always used -e STORAGE=“” on the docker run to ‘force’ the value from my config.yaml as this allows a change with a simple restart (which a software update does) rather than a delete & re-create (which I have to do!)

Alexey · April 23, 2026, 6:46am

move storagenode-docker from storj/storj · storj/storagenode-docker@61acd11 · GitHub so, almost 4 years ago.

Please use "" instead of “” in this variable, i.e.: -e STORAGE="" before the container image, but you must recreate a container to apply this change.

You may also just provide as big value as possible and manage the allocation by the storage quota on your storage volume. The node will select a minimum between specified and used+available on restart.

Tempest · April 23, 2026, 7:05am

Yes I have this parameter defined in my run command which reflected in my config file I showed. Nothing was changed, I only updated the version.

docker run -d --restart always --stop-timeout 300
-p 28968:28967/tcp
-p 28968:28967/udp
-p 14002:14002
-e WALLET=“private”
-e EMAIL="private@gmail.com"
-e ADDRESS=“private.com:28968”
-e STORAGE=“13TB”
–mount type=bind,source=“/mnt/exos16tb/storj/storagenode1/identity/storagenode”,destination=/app/identity
–mount type=bind,source=“/mnt/exos16tb/storj/storagenode1”,destination=/app/config
–name storagenode storjlabs/storagenode:latest

Alexey · April 23, 2026, 7:56am

If there are no characters like “13TB” and you have it actually like "13TB", then it should work. However, for these parameters, which are env variables prefixed with -e option, you need to stop and remove the container, then run it back using all your parameters, including the changed ones.

Note that Docker doesn’t like changes to the bind filesystem when the container is stopped because it uses an overlay filesystem, so it may revert your changes when you restart the container (we’ve seen this happen many times).
So it’s always required to stop and remove the container, apply a modification, then run it back.