Node with less than 500gb

I have no idea if this means anything: but I’ve had “storjlabs/storagenode:latest” at the end of my commands (so all the “–flag” stuff comes before it).

Edit: and this may be a cut-and-paste thing… but your final “–operator.” flag starts with an em-dash/long-hypen instead of "--"

Yeah, that’s the way to go if you want to arrange everything in the config file. But if you want to manage it with the docker statement, you have to do it this way. So, after the name comes the storagenode --flag stuff.

The error actually says: I’m missing necesarry keys.
And I’m quite sure TS should get some errors when he’s running the code he posts above.

Pleas, @andrijajepro , put your docker statement between ``` at the beginning and the end (triple!)

unknown flag: --storage2.monitor.minimum-disk-space
See ‘docker run --help’.

I got this now, after puting name after (your edit)

Again, post your docker run statement between ```!

So, shouldn’t be done… As I said above :wink:

So again:

docker run -d --restart unless-stopped --stop-timeout 300 \
                -p 28967:28967/tcp \
                -p 28967:28967/udp \
                -p 14002:14002 \
                -e WALLET="$sWallet" \
                -e EMAIL="$sEmail" \
                -e ADDRESS="$sAddress" \
                -e STORAGE="10GB" \
                --user $(id -u):$(id -g) \
                --mount type=bind,source="$sIDFolder",destination=/app/identity \
                --mount type=bind,source="$sNodeMnt",destination=/app/config \
                --name "storagenode" storjlabs/storagenode:latest \
                --storage2.monitor.minimum-disk-space="1MiB"

\ at the end of each line
–storagenode.options.lines after --name

docker run -d --restart unless-stopped --stop-timeout 300                 -p 28967:28967/tcp                 -p 28967:28967/udp                 -p 14002:14002                 -e WALLET="0x582e0Fce6bc6ea7f08b175eFF5760744Ff114a76"                 -e EMAIL="xxxxxx@gmail.com"                 -e ADDRESS="xxxxx:28967"                -e STORAGE="10GB"                               --mount type=bind,source=/storj/identity/storagenode,destination=/app/identity                 --mount type=bind,source=/storj/data,destination=/app/config                                  --storage2.monitor.minimum-disk-space="1MiB" \ --operator.wallet-features=zksync  --name "storagenode4" storjlabs/storagenode:latest
unknown flag: --storage2.monitor.minimum-disk-space
See 'docker run --help'.

What is this --user?

Everything on one line?
What about

docker run -d --restart unless-stopped --stop-timeout 300
                 -p 28967:28967/tcp \
                 -p 28967:28967/udp \
                 -p 14002:14002 \
                 -e WALLET="0x582e0Fce6bc6ea7f08b175eFF5760744Ff114a76" \ 
                 -e EMAIL="xxxxxx@gmail.com" \ 
                 -e ADDRESS="xxxxx:28967" \ 
                 -e STORAGE="10GB" \
                 --mount type=bind,source=/storj/identity/storagenode,destination=/app/identity \
                 --mount type=bind,source=/storj/data,destination=/app/config \
                 --name "storagenode4" storjlabs/storagenode:latest \
                 --storage2.monitor.minimum-disk-space="1MiB" \
                 --operator.wallet-features=zksync

Storage Node - Storj Docs
Only necessary if you run it with another user than root.

It apparantly works?

10GB? You need at least 500 for the node to start.

I think he’s using the storage2.monitor.minimum-disk-space param to override that check.

2 Likes

Ah I missed that in his unreadable post.

2 Likes

Now it just restarts, same log

Well, I pity you.
Especially since you don’t seem to help yourself by showing any information. And I seem to need to ask everytime exactly the same. So, help yourself and do it yourself; I’m not asking again.

1 Like

You need to remove the old node first. But seriously, there has been a tonne of good help in this thread.

1 Like