Installing Prysm with docker
Prysm can be installed on Windows, GNU/Linux, MacOS systems with Docker. This page includes instructions for performing this method.
Pro-Tip
The Prysm installation script is the easiest and most efficient way of installing the latest binaries. Instructions for using it can be found here.
Have questions? Stop by the #documentation channel on Discord and let us know.
System requirements
Minimum specifications
These specifications must be met in order to successfully run the Prysm client.
- Operating System: 64-bit Linux, Mac OS X 10.14+, Windows 64-bit
- Processor: Intel Core i5โ760 or AMD FX-8100 or better
- Memory: 8GB RAM
- Storage: 20GB available space SSD
- Internet: Broadband connection
Recommended specifications
These hardware specifications are recommended, but not required to run the Prysm client.
- Processor: Intel Core i7โ4770 or AMD FX-8310 or better
- Memory: 16GB RAM
- Storage: 100GB available space SSD
- Internet: Broadband connection
Dependencies
- A modern operating system
- The latest release of Docker installed
Installing Prysm
- Linux
- Windows
- MacOS
- Ensure you are running the most recent version of Docker by issuing the command:
- To pull the Prysm images, issue the following commands:
This process will also install any related dependencies.
Pro-Tip
For advanced users, the beacon-chain and validator images with debugging tools bundled in can be fetched instead by appending -alpine
to the end of the images in the pull
commands above. For example: docker pull .../prysm/validator:latest-alpine
.
Now that your installation is done, you can then read joining eth2.
Managing the beacon node with Docker
Below are various methods of controlling the beacon node in Docker installations.
The beacon node can be halted by either using Ctrl+c
or with the command:
To restart the beacon node, issue the following command:
To delete a corrupted container, issue the following command:
To recreate a deleted container and refresh the chain database, issue the start command with an additional --clear-db
parameter where <YOUR_ETH1_NODE_ENDPOINT> is in the format of an http endpoint such as http://host:port
(ex: http://localhost:8545
for geth) or an IPC path such as /path/to/geth.ipc
: