How Eth-Docker Works on Hardware Reboot | Eth-Docker Setup Highlight

EthStaker Special Events · November 2020 · 3:07

An EthStaker community walkthrough covers how Eth-Docker behaves after a hardware reboot, focusing on the Docker Compose based setup that runs Ethereum execution and consensus clients for solo staking. It highlights what operators should expect from their validator and client containers once the underlying machine restarts.

Speakers

Topics

From EthStaker Special Events, hosted by Eth Staker.

Transcript

what happens if um i need to restart my machine like that does it all restart by itself or like how does it plus indeed yes um everything will restart when you restart the machine um unless you stopped it so if i do an ft stop here it will not come up right the reason for this is that we have a restart variable somewhere in here unless restart equals unless stopped this can also be set to restart always then it would always restart even if it has been stopped that can be interesting some people are like maybe i stopped it and then at least when i reboot the machine it comes back right but the default is unless stopped

meaning it will always get restarted unless you as the user deliberately stop the thing what i like to do uh especially when it comes to something like a validator or a validator or a test net is after i stop it i like to reboot the machine and then do a docker ps to see if it came up because you you don't want those sneaky processes running in the background and you've forgotten about them because a docker image or can run in the background for months and years and you may not even be aware of it correct superfiz you wanted to know that this is gone gone right so i expect to still see the things that were running previously two containers that were not in f docker and there they are i have a sepolia ed

docker test is actually one is george who's was trying teku and then this over here is a geth that's running on sepula those two were there before but the docker stuff itself is gone it is not running at this point if i want to run it again just go in here and say sd up and i can see that it is bringing all that back up and now my docker ps is a lot busier so i'm confused i thought it would restart it does not because we stopped it oh stop and then we reboot it right so now we can do this again with not as running reboot and maybe talk some more

and see that it cut that it is back up if i'm not manually stopping it so superfizz's point was if i recall correctly superfiz um if i stop this because i meant to stop it i don't want it to come back up when i'm rebooting that's scary right is that right was that what he was right that was your point right and now we're doing the opposite we're saying if i have it running and i have an automated reboot power outage or just an automated reboot because i'm doing unattended upgrades and i don't want to worry about linux upgrades and i let it do that right all that stuff i do not want to worry in that case about it not coming back up so

we'll see that here basically the way f docker behaves out of the box is it goes with your choice if you have it running it keeps running after reboot if you stopped it it stays stopped after reboot