The 'beacon-chain' container stops and no longer works

[lzmrd]

Description

I'm tryning to setup a private network through this repo. It works for me with this docker-compose.yml:

version: "3.9"
services:
  #Creates a genesis state for the beacon chain using a YAML configuration file and
  # a deterministic set of 64 validators.
  create-beacon-chain-genesis:
    image: "gcr.io/prysmaticlabs/prysm/cmd/prysmctl:HEAD-aec349"
    command:
      - testnet
      - generate-genesis
      - --fork=capella
      - --num-validators=64
      - --genesis-time-delay=15
      - --output-ssz=/consensus/genesis.ssz
      - --chain-config-file=/consensus/config.yml
      - --geth-genesis-json-in=/execution/genesis.json
      - --geth-genesis-json-out=/execution/genesis.json
    volumes:
      - ./consensus:/consensus
      - ./execution:/execution

  create-beacon-node-keys:
    image: "alpine:latest"
    command:
      - ./consensus/init.sh
    volumes:
      - ./consensus:/consensus
      - ./execution:/execution

  erigon-genesis:
    image: "thorax/erigon:latest"
    command: --datadir=/execution/erigon init /execution/genesis.json
    volumes:
      - ./execution:/execution
      - ./execution/genesis.json:/execution/genesis.json
    depends_on:
      create-beacon-chain-genesis:
        condition: service_completed_successfully

  beacon-chain:
    image: "gcr.io/prysmaticlabs/prysm/beacon-chain:v4.2.0"
    command:
      - --datadir=/consensus/beacondata-2
      - --min-sync-peers=0
      - --genesis-state=/consensus/genesis.ssz
      - --interop-eth1data-votes
      - --chain-config-file=/consensus/config.yml
      - --contract-deployment-block=0
      - --chain-id=${CHAIN_ID:-32382}
      - --rpc-host=0.0.0.0
      - --grpc-gateway-host=0.0.0.0
      - --execution-endpoint=http://erigon:8551
      - --accept-terms-of-use
      - --jwt-secret=/execution/jwtsecret
      - --suggested-fee-recipient=0x85da99c8a7c2c95964c8efd687e95e632fc533d6
      - --minimum-peers-per-subnet=0
      - --enable-debug-rpc-endpoints
      - --p2p-tcp-port=13001
    depends_on:
      create-beacon-chain-genesis:
        condition: service_completed_successfully
      create-beacon-node-keys:
        condition: service_completed_successfully
    ports:
      - 13001:13001
    volumes:
      - ./consensus:/consensus
      - ./execution:/execution
      - ./execution/jwtsecret:/execution/jwtsecret
    networks:
      polygon-net:
        ipv4_address: 10.100.100.11

  # Runs the go-ethereum execution client with the specified, unlocked account and necessary
  # APIs to allow for proof-of-stake consensus via Prysm.
  erigon:
    image: "thorax/erigon:latest"
    command:
      - --http
      - --http.api=eth,net,web3,erigon,engine,debug
      - --http.addr=0.0.0.0
      - --http.corsdomain=*
      - --ws
      - --authrpc.vhosts=*
      - --authrpc.addr=0.0.0.0
      - --authrpc.jwtsecret=/execution/jwtsecret
      - --datadir=/execution/erigon
      - --nat=extip:10.100.100.13
      - --db.size.limit=1GB
      - --networkid=32382
    ports:
      - 8551:8551
      - 8545:8545
      - 8546:8546
    depends_on:
      erigon-genesis:
        condition: service_completed_successfully
      beacon-chain:
        condition: service_started
    volumes:
      - ./execution:/execution
      - ./execution/jwtsecret:/execution/jwtsecret
    networks:
      polygon-net:
        ipv4_address: 10.100.100.13


  # We run a validator client with 64, deterministically-generated keys that match
  # The validator keys present in the beacon chain genesis state generated a few steps above.
  validator:
    image: "gcr.io/prysmaticlabs/prysm/validator:v4.2.0"
    command:
      - --beacon-rpc-provider=beacon-chain:4000
      - --datadir=/consensus/validatordata
      - --accept-terms-of-use
      - --interop-num-validators=64
      - --interop-start-index=0
      - --chain-config-file=/consensus/config.yml
    depends_on:
      beacon-chain:
        condition: service_started
    volumes:
      - ./consensus:/consensus
    networks:
      polygon-net:
        ipv4_address: 10.100.100.14

networks:
  polygon-net:
    driver: bridge
    ipam:
      config:
      - subnet: 10.100.100.0/24

Version

"com.docker.compose.version": "2.28.1",
"desktop.docker.io/wsl-distro": "Ubuntu-22.04",
erigon version 3.00.0-dev-6231a931,

Present Behaviour

The chain works, but I have a problem with "beacon-chain". If "erigon" or "validator" stop, I can start again them with no problems for the chain. The issue comes when "beacon-chain" stops. I can start it again but it is not going to work again.
Here are some logs:

2024-08-01 11:59:24 time="2024-08-01 09:59:24" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 11:59:24 time="2024-08-01 09:59:24" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 11:59:38 time="2024-08-01 09:59:38" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 11:59:38 time="2024-08-01 09:59:38" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 11:59:52 time="2024-08-01 09:59:52" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 11:59:52 time="2024-08-01 09:59:52" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 12:00:06 time="2024-08-01 10:00:06" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 12:00:06 time="2024-08-01 10:00:06" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 12:00:12 time="2024-08-01 10:00:12" level=info msg="Peer summary" activePeers=0 inbound=0 outbound=0 prefix=p2p
2024-08-01 12:00:20 time="2024-08-01 10:00:20" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 12:00:20 time="2024-08-01 10:00:20" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 12:00:27 time="2024-08-01 10:00:27" level=error msg="could not process new slot" error="0x0000000000000000000000000000000000000000000000000000000000000000: unknown finalized root" prefix=blockchain
2024-08-01 12:00:34 time="2024-08-01 10:00:34" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 12:00:34 time="2024-08-01 10:00:34" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 12:00:48 time="2024-08-01 10:00:48" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 12:00:48 time="2024-08-01 10:00:48" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 12:01:02 time="2024-08-01 10:01:02" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 12:01:02 time="2024-08-01 10:01:02" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 12:01:12 time="2024-08-01 10:01:12" level=info msg="Peer summary" activePeers=0 inbound=0 outbound=0 prefix=p2p
2024-08-01 12:01:16 time="2024-08-01 10:01:16" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 12:01:16 time="2024-08-01 10:01:16" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 12:01:30 time="2024-08-01 10:01:30" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 12:01:30 time="2024-08-01 10:01:30" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 12:01:39 time="2024-08-01 10:01:39" level=error msg="could not process new slot" error="0x0000000000000000000000000000000000000000000000000000000000000000: unknown finalized root" prefix=blockchain
2024-08-01 12:01:44 time="2024-08-01 10:01:44" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 12:01:44 time="2024-08-01 10:01:44" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 12:01:58 time="2024-08-01 10:01:58" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 12:01:58 time="2024-08-01 10:01:58" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 12:02:12 time="2024-08-01 10:02:12" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 12:02:12 time="2024-08-01 10:02:12" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 12:02:12 time="2024-08-01 10:02:12" level=info msg="Peer summary" activePeers=0 inbound=0 outbound=0 prefix=p2p
2024-08-01 12:02:26 time="2024-08-01 10:02:26" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 12:02:26 time="2024-08-01 10:02:26" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 12:02:40 time="2024-08-01 10:02:40" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 12:02:40 time="2024-08-01 10:02:40" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 12:02:51 time="2024-08-01 10:02:51" level=error msg="could not process new slot" error="0x0000000000000000000000000000000000000000000000000000000000000000: unknown finalized root" prefix=blockchain
2024-08-01 12:02:54 time="2024-08-01 10:02:54" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 12:02:54 time="2024-08-01 10:02:54" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 12:03:08 time="2024-08-01 10:03:08" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 12:03:08 time="2024-08-01 10:03:08" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain
2024-08-01 12:03:12 time="2024-08-01 10:03:12" level=info msg="Peer summary" activePeers=0 inbound=0 outbound=0 prefix=p2p
2024-08-01 12:03:22 time="2024-08-01 10:03:22" level=warning msg="Execution client is not syncing" prefix=powchain
2024-08-01 12:03:22 time="2024-08-01 10:03:22" level=error msg="Beacon node is not respecting the follow distance" prefix=powchain

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?