We are using docker-compose with persistent volume to start sawtooth-validator with sawtooth-pbft and other TPs .We are using a persistent volume for the same , so that it can be used for backup. Here is our yaml for the same
validator:
build: validator/.
image: hyperledger/sawtooth-validator:1.1.5
container_name: sawtooth-validator
expose:
- 4004
- 5050
- 8800
volumes:
- volume1:/var/lib/sawtooth/
- keys:/etc/sawtooth/keys
ports:
- "8800:8800"
command: |
bash -c "
sawtooth-validator -vv \
"
Now when we start the docker-compose with the -d (docker-compose up -d )option, it doesn't take any new transactions. But if we do the same without the -d option (docker-compose up) it works fine . What may be the cause of the issue ? why docker-compose behaves differently with -d option?
To me , It looks like the validator is not able to get validate the new incoming blocks say x beacause it is not able to get the block x-1 from the persistent volume in the detached mode ? Which it is able to do in the normal mode. Is there some permission difference between detached mode and normal mode?