StakeSquid/ethereum-rpc-docker
1
0
Fork 0
Code Issues 1 Packages Projects Releases Wiki Activity

fix

Browse Source
This commit is contained in:
squidbear
2025-03-29 08:27:45 +01:00
parent 3ca021b6c8
commit 2b82a11bcf
4 changed files with 44 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
berachain/reth/berachain-bepolia-reth-archive-trace.yml
View File

@@ -1,3 +1,14 @@
# this is what you should know:
# the execution client can not start before the node part initialized and generated a genesis block for the execution client
# once the execution client is started it needs a push from the node to start syncing but then syncs p2p
# if you restart the node then the node willnot start anymore because the execution client is syncing
# but the execution client stops syncing if it doesn't get a node to push it.
# delete and resync. idk what's the solution honestly
# rm -rf berachain/mainnet/config/* && rm -rf /var/lib/docker/volumes/rpc_berachain-mainnet-reth-archive-trace*/_data/* && ./force-recreate.sh berachain-mainnet-archive
# I also suspect that the peers will blacklist you frequently if you try more than once
services:
berachain-bepolia-archive:
image: ghcr.io/paradigmxyz/reth:${RETH_VERSION:-v1.3.4}
@@ -65,7 +76,6 @@ services:
- "CHAINNAME=bepolia"
- "CHAINID=80069"
- "AUTH_RPC=http://berachain-bepolia-archive:8551"
- "AUTH_RPC=http://berachain-bepolia-archive:8545"
- "CHAIN_SPEC=testnet"
entrypoint: [ "sh", "/init.sh" ]
networks:

12
berachain/reth/berachain-bepolia-reth-pruned-trace.yml
View File

@@ -1,3 +1,14 @@
# this is what you should know:
# the execution client can not start before the node part initialized and generated a genesis block for the execution client
# once the execution client is started it needs a push from the node to start syncing but then syncs p2p
# if you restart the node then the node willnot start anymore because the execution client is syncing
# but the execution client stops syncing if it doesn't get a node to push it.
# delete and resync. idk what's the solution honestly
# rm -rf berachain/mainnet/config/* && rm -rf /var/lib/docker/volumes/rpc_berachain-mainnet-reth-archive-trace*/_data/* && ./force-recreate.sh berachain-mainnet-archive
# I also suspect that the peers will blacklist you frequently if you try more than once
services:
berachain-bepolia:
image: ghcr.io/paradigmxyz/reth:${RETH_VERSION:-v1.3.4}
@@ -65,7 +76,6 @@ services:
- "CHAINNAME=bepolia"
- "CHAINID=80069"
- "AUTH_RPC=http://berachain-bepolia:8551"
- "AUTH_RPC=http://berachain-bepolia:8545"
- "CHAIN_SPEC=testnet"
entrypoint: [ "sh", "/init.sh" ]
networks:

12
berachain/reth/berachain-mainnet-reth-archive-trace.yml
View File

@@ -1,3 +1,14 @@
# this is what you should know:
# the execution client can not start before the node part initialized and generated a genesis block for the execution client
# once the execution client is started it needs a push from the node to start syncing but then syncs p2p
# if you restart the node then the node willnot start anymore because the execution client is syncing
# but the execution client stops syncing if it doesn't get a node to push it.
# delete and resync. idk what's the solution honestly
# rm -rf berachain/mainnet/config/* && rm -rf /var/lib/docker/volumes/rpc_berachain-mainnet-reth-archive-trace*/_data/* && ./force-recreate.sh berachain-mainnet-archive
# I also suspect that the peers will blacklist you frequently if you try more than once
services:
berachain-mainnet-archive:
image: ghcr.io/paradigmxyz/reth:${RETH_VERSION:-v1.3.4}
@@ -65,7 +76,6 @@ services:
- "CHAINNAME=mainnet"
- "CHAINID=80094"
- "AUTH_RPC=http://berachain-mainnet-archive:8551"
- "AUTH_RPC=http://berachain-mainnet-archive:8545"
- "CHAIN_SPEC=mainnet"
entrypoint: [ "sh", "/init.sh" ]
networks:

12
berachain/reth/berachain-mainnet-reth-pruned-trace.yml
View File

@@ -1,3 +1,14 @@
# this is what you should know:
# the execution client can not start before the node part initialized and generated a genesis block for the execution client
# once the execution client is started it needs a push from the node to start syncing but then syncs p2p
# if you restart the node then the node willnot start anymore because the execution client is syncing
# but the execution client stops syncing if it doesn't get a node to push it.
# delete and resync. idk what's the solution honestly
# rm -rf berachain/mainnet/config/* && rm -rf /var/lib/docker/volumes/rpc_berachain-mainnet-reth-archive-trace*/_data/* && ./force-recreate.sh berachain-mainnet-archive
# I also suspect that the peers will blacklist you frequently if you try more than once
services:
berachain-mainnet:
image: ghcr.io/paradigmxyz/reth:${RETH_VERSION:-v1.3.4}
@@ -65,7 +76,6 @@ services:
- "CHAINNAME=mainnet"
- "CHAINID=80094"
- "AUTH_RPC=http://berachain-mainnet:8551"
- "AUTH_RPC=http://berachain-mainnet:8545"
- "CHAIN_SPEC=mainnet"
entrypoint: [ "sh", "/init.sh" ]
networks: