Sawtooth Docker Compose file issue on `bash -c` multi-line string commands

[houluy]

I'm trying to run sawtooth PBFT or PoET testing network by docker compose. The official yaml file has some problems on all the multi-line commands of bash -c with backslash symbol to break line, for example, in sawtooth-default-pbft.yaml, the validator-0 has a command configuration with multi-line bash commands, where the string sawset proposal create \ -k /etc/sawtooth/keys/validator.priv \ sawtooth.consensus.algorithm.name=pbft \ sawtooth.consensus.algorithm.version=1.0 \ seems to be incorrect during execution. 'command not found' errors will occur. Besides, the compose process will stuck at some point, and the curl command in shell result in connection refused. It means that the sawtooth network is not established correctly. However, after changing all the multi-line commands into one line, and remove all the backslash symbols, the sawtooth network is established successfully. I think the backslash may be misused. This may cause confusion to those who deploy sawtooth test network for the first time.

In all, to run the sawtooth docker compose correctly, replacing all the multi-line command string in yaml file into single line, and remove all the backslash symbols that are used for line breaking.

[jallard302]

Hi there, I ran into the same issues myself, this is due to the stringent requirements of the .yaml formatting system within the docker-compose.yaml files. I needed to make the slashed "command" arguments single line so that yaml could read it properly and it got the network running. You also need to remove most slashes from the "sawtooth.consensus.pbft.members=" decleration within the "sawset proposal create -k" command towards the middle of the validator-0 container bash script. This is because this command passes on the public keys of each validator into the PBFT consensus engine containers in a .json format which will throw up errors if the extra slashes are included. I'll attach a .txt file of the "corrected" docker-compose file for the PBFT network which ensures all containers run and I've got all except the intkey-tp and xo-tp containers running (this is my current issue) and it will allow you to do basic transactions on the testnet. I know this reply is over a year late but I want to put this up for anyone else attempting to use the testnet. Cheers.

sawtooth-test-pbft-backup.txt