Skip to main content

Install Prysm with Docker

Prysm can be installed on Windows, GNU/Linux, and MacOS systems with Docker. We use Bazel to push preconfigured Docker images to a publicly accessible Google Cloud container registry.

Not familiar with Docker? Try our quickstart

This guidance is targeted at users who are already comfortable with Docker. See our Quickstart for beginner-friendly installation instructions.

Select a configuration:

Review system requirements#

  • OS: 64-bit Linux, Mac OS X 10.14+, Windows 64-bit
  • CPU: Intel Core i5–760 or AMD FX-8100 or better
  • Memory: 8GB RAM
  • Storage: SSD with 20GB+ available
  • Internet: Broadband connection
  • Software: The latest release of Docker installed.
  • CPU: Intel Core i7–4770 or AMD FX-8310 or better
  • Memory: 16GB RAM
  • Storage: SSD with 100GB+ available

Download the Prysm Docker images#

First, ensure that you're running the most recent version of Docker:

docker -v

Next, pull the Prysm images:

## stable, without Busybox debugging toolsdocker pull pull
## latest, without Busybox debugging toolsdocker pull pull
## latest, with Busybox debugging toolsdocker pull pull

These commands will automatically install dependencies.

Configure ports (optional)#

We recommend opening up ports tcp/13000 and udp/12000 on your router and firewall to improve peer-to-peer connectivity. Refer to your operating system and router documentation for port configuration instructions. With this complete, appending --p2p-host-ip=$(curl -s to your beacon node startup command will configure Prysm to use your newly opened ports. Refer to Configure ports and firewalls for more information.

Run a beacon node#

Knowledge Check

Not familiar with nodes, networks, and related terminology? Consider reading Nodes and networks before proceeding.

If you're not already running an execution node, refer to our Quickstart for beginner-friendly execution node installation instructions.

Next, use Docker to tell your beacon node to connect to your local execution node. Note that <YOUR_ETH_EXECUTION_NODE_ENDPOINT> is either an HTTP endpoint http://host:port or an IPC path such as /path/to/geth.ipc.

docker run -it -v $HOME/.eth2:/data -p 4000:4000 -p 13000:13000 -p 12000:12000/udp --name beacon-node \ \  --datadir=/data \  --jwt-secret=<YOUR_JWT_SECRET> \  --rpc-host= \  --grpc-gateway-host= \  --monitoring-host= \  --execution-endpoint=<YOUR_ETH_EXECUTION_NODE_ENDPOINT>

Run a validator#

Ensure that you're not running multiple instances of the same validator public key, especially if you're using scripts or other forms of automation. If the Ethereum network detects two instances of the same validator key submitting proposals, attestations, or votes, it may assume malicious intent and slash accordingly.

Verify that your beacon node and execution node are both fully synced. If you're not fully synced, you risk being penalized and losing some of your staked ETH.

Check the sync status of your node with the following command:

curl http://localhost:3500/eth/v1alpha1/node/syncing

If your node is done synchronizing, you will see the response:


Stake your ETH#

Exercise caution

The Ethereum launchpad URL is and the only, official validator deposit contract is 0x00000000219ab540356cbb839cbe05303d7705fa. Don't send ETH directly to the contract - deposit your stake through launchpad.

Use the Mainnet Launchpad to deposit your 32 ETH. If you want to participate in the testnet, use the Goerli-Prater or Ropsten launchpads.

Throughout the process, you'll be asked to generate new validator credentials using the official Ethereum deposit command-line-tool. Make sure you use the mainnet option when generating keys with the deposit CLI. During the process, you will have generated a validator_keys folder under the eth2.0-deposit-cli directory. You can import all of your validator keys into Prysm from that folder in the next step.

Import keystores#

Copy the path to the validator_keys folder under the eth2.0-deposit-cli directory you created during the launchpad process and issue the following command:

docker run -it -v $HOME/eth2.0-deposit-cli/validator_keys:/keys \  -v $HOME/Eth2Validators/prysm-wallet-v2:/wallet \  --name validator \  --accept-terms-of-use \ \  accounts import --keys-dir=/keys --wallet-dir=/wallet

Run validator#

Open a second terminal window. Issue the following command to start the validator:

docker run -it -v $HOME/Eth2Validators/prysm-wallet-v2:/wallet \  -v $HOME/Eth2:/validatorDB \  --network="host" --name validator \ \  --beacon-rpc-provider= \  --wallet-dir=/wallet \  --datadir=/validatorDB

You’re now running a full Ethereum node and a validator.

It can a long time (from days to months) for your validator to become fully activated. To learn more about the validator activation process, see Deposit Process. See Check node and validator status for detailed status monitoring guidance.

You can leave your execution client, beacon node, and validator client terminal windows open and running. Once your validator is activated, it will automatically begin proposing and validating blocks.

Appendix A: Manage Prysm with Docker#

To interact with your beacon node through Docker, use one of the following commands:

  • Halt: docker stop beacon-node or Ctrl+c
  • Restart: docker start -ai beacon-node
  • Delete: docker rm beacon-node

To recreate a deleted container and refresh the chain database, issue the start command with an additional --clear-db parameter, where <YOUR_ETH_EXECUTION_NODE_ENDPOINT> is in the format of an http endpoint such as http://host:port (ex: http://localhost:8551 for Geth) or an IPC path such as /path/to/geth.ipc:

docker run -it -v $HOME/.eth2:/data -p 4000:4000 -p 13000:13000 -p 12000:12000/udp --name beacon-node \ \  --datadir=/data \  --clear-db \  --rpc-host= \  --monitoring-host= \  --execution-endpoint=<YOUR_ETH_EXECUTION_NODE_ENDPOINT> 

Frequently asked questions#

Why do we set --rpc-host and --grpc-gateway-host to
This tells your Docker container to to "listen" for connections from outside of your container, allowing you (and other services) to reach your RPC endpoint(s). See Configure ports and firewalls for more information.