0xWilliamWang
commented
2 months ago add couple of "beacon-chain"s more You can initialize el data on the host first, then start el-cl. eg:
init() { initCL initEL return }
initCL() { rm -rf ./conf/consensus/genesis.ssz* prysmctl \ testnet \ generate-genesis \ --chain-config-file=./conf/consensus/config.yml \ --deposit-json-file=./deposit.json \ --config-name=b2hub \ --num-validators=64 \ --genesis-time=0x0 \ --genesis-time-delay=20 \ --geth-genesis-json-in=./conf/execution/genesis.json \ --geth-genesis-json-out=./conf/execution/genesis.json \ --output-ssz=./conf/consensus/genesis.ssz \ --output-json=./conf/consensus/genesis.ssz.json \ --fork=deneb return }
initEL() { geth version for item in $(seq -f 'node%g' 1 $NODE_NUM); do geth --datadir=./l1-tmp-data/$item/execution \ init \ ./conf/execution/genesis.json mkdir -p l1-tmp-data/$item/consensus/beacon done return }
Description
I'm trying to setup a private network through this repo. It works for me with this docker-compose.yml:
Version
"com.docker.compose.version": "2.28.1", "desktop.docker.io/wsl-distro": "Ubuntu-22.04",
Present Behaviour
The chain works, but I have a problem with "beacon-chain". If "geth" or "validator" stop, I can start them again with no problems for the chain. The issue comes when "beacon-chain" stops. I can start it again but it is no longer working. Here are some logs. Beacon-chain:
geth:
validator:
Steps to resolve
What I'd like to do is to modify the docker-compose.yml file in order to add couple of "beacon-chain"s more. In this way if one of them goes down there are others to follow the chain. Unfortunatly I'm a newbie with Docker and I cannot set it up. Can someone trying to help me in that, or at least, tell me if it is a possible configuration?