2

The docker implementation with tezos is bad. https://gitlab.com/tezos/tezos/-/issues/548 It does not allow for many configuration parameters to be customized, and hard-codes many parameters too. For your specific case, this can be solved by using an external mountpoint as the storage for the node like this: -v /opt/tezos/node_data:/var/run/node/data Start ...


1

For high availability, you should already have a 2nd tezos-node running and sync'd with the network. If you need to move baking operations to the backup server, best is to copy the ~/.tezos-client/ directory from server A to server B. Then you can start the baker/endorser on server B. You will be punished HARD if you double bake or double endorse so make ...


1

For that step you'll need to edit the content of the two file mentioned, replacing <proto> in the name with the protocol you intend to use, and setting the alias(es) to the BAKER_ACCOUNT and ENDORSER_ACCOUNT options in them. For example (at the time of writing, Ubuntu packages version 9.0-1), if you are using edo2net and the alias for your baker ...


1

You need to be sure you're running PtEdo2Zk tezos-baker and tezos-endorser instead of PtEdoTez. Your tezos-baker should at least provide low priority baking rights.


Only top voted, non community-wiki answers of a minimum length are eligible