Only do this in emergencies, such as when eth2 is not syncing or RAM/CPU use is spiking. This procedure can be used for Prysm or Lighthouse.
The specific client versions mentioned here are for RocketPool 0.0.8. They will not work in prior versions of RP.
Edit config.yml:
cd ~/.rocketpool
cp config.yml config.yml.original
nano config.yml
For Prysm you need the debug image so that sh
is present.
Find the new image you wish to use at docker hub for beacon and validator
Change eth2 prysm section to use new image, for example:
- id: prysm
name: Prysm
beaconImage: prysmaticlabs/prysm-beacon-chain:HEAD-b150ac-debug #v1.0.2
validatorImage: prysmaticlabs/prysm-validator:HEAD-fc7c67-debug #v1.0.3
desc: made by Prysmatic Labs
link: https://prysmaticlabs.com/
Courtesy of @Mentor, you can use this command to make the change for you:
cp ~/.rocketpool/config.yml ~/.rocketpool/config-before-manual-prysm-update.yml.bak && \
sed -i 's/\(prysm-beacon-chain:\).*$/\1HEAD-b150ac-debug # MANUAL OVERRIDE/g' ~/.rocketpool/config.yml && \
sed -i 's/\(prysm-validator:\).*$/\1HEAD-fc7c67-debug # MANUAL OVERRIDE/g' ~/.rocketpool/config.yml
You can use a newer release tag from the docker hub image.
Change lighthouse prysm section to use new image, for example:
- id: lighthouse
name: Lighthouse
desc: made by Sigma Prime
image: sigp/lighthouse:latest
link: https://sigmaprime.io/
If you are coming from a version prior to v1.0.0, you'll need to edit ~/.rocketpool/chains/eth2/start-beacon.sh
as well as ~/.rocketpool/chains/eth2/start-validator.sh
and replace --testnet pyrmont
with --network pyrmont
If using Lighthouse latest
, force docker to pull it:
docker image pull sigp/lighthouse:latest
Pause and start rocketpool, you expect to see it pulling the new image if using Prysm:
rocketpool service pause && rocketpool service start
Follow eth1 logs:
rocketpool service logs eth1
Once eth1 is synced follow eth2 logs and see whether it syncs:
rocketpool service logs eth2
Yeah this was a great help,all green and no missed att for the last 6 hours