From 5228ebf34041860371472ec7ca07988a0d0ddea8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Toni=20Ram=C3=ADrez?= <58293609+ToniRamirezM@users.noreply.github.com> Date: Mon, 21 Aug 2023 17:13:29 +0200 Subject: [PATCH] Update prover images (#2432) * update prover images * update prover images * update prover images --- docker-compose.yml | 2 +- docs/production-setup.md | 2 +- test/docker-compose.yml | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docker-compose.yml b/docker-compose.yml index 0755564b29..9ad2bf0908 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -107,7 +107,7 @@ services: zkevm-prover: container_name: zkevm-prover restart: unless-stopped - image: hermeznetwork/zkevm-prover:v2.0.1 + image: hermeznetwork/zkevm-prover:v2.0.1-hotfix.1 depends_on: zkevm-state-db: condition: service_healthy diff --git a/docs/production-setup.md b/docs/production-setup.md index 1d66ee8e56..b3c32e5e97 100644 --- a/docs/production-setup.md +++ b/docs/production-setup.md @@ -41,7 +41,7 @@ Explained step by step: 2. Define installation path: `ZKEVM_DIR=./path/to/install` 3. Define a config directory: `ZKEVM_CONFIG_DIR=./path/to/config` 4. It's recommended to source this env vars in your `~/.bashrc`, `~/.zshrc` or whatever you're using -5. Download and extract the artifacts: `curl -L https://github.com/0xPolygonHermez/zkevm-node/releases/latest/download/$ZKEVM_NET.zip > $ZKEVM_NET.zip && unzip -o $ZKEVM_NET.zip -d $ZKEVM_DIR && rm $ZKEVM_NET.zip`. Note you may need to install `unzip` for this command to work +5. Download and extract the artifacts: `curl -L https://github.com/0xPolygonHermez/zkevm-node/releases/latest/download/$ZKEVM_NET.zip > $ZKEVM_NET.zip && unzip -o $ZKEVM_NET.zip -d $ZKEVM_DIR && rm $ZKEVM_NET.zip`. Note you may need to install `unzip` for this command to work. Also take into account this works for the latest release, in case you want to deploy a pre-release you should get the artifacts directly for that release and not using the "latest" link depicted here. [Here](https://github.com/0xPolygonHermez) you can check the node version deployed for each network. 6. Copy the file with the env parameters: `cp $ZKEVM_DIR/$ZKEVM_NET/example.env $ZKEVM_CONFIG_DIR/.env` 7. Edit the env file, with your favourite editor. The example will use nano: `nano $ZKEVM_CONFIG_DIR/.env`. This file contains the configuration that anyone should modify. For advanced configuration: 1. Copy the config files into the config directory `cp $ZKEVM_DIR/$ZKEVM_NET/config/environments/testnet/* $ZKEVM_CONFIG_DIR/` diff --git a/test/docker-compose.yml b/test/docker-compose.yml index 3abb33ed0c..599f2c84a8 100644 --- a/test/docker-compose.yml +++ b/test/docker-compose.yml @@ -338,7 +338,7 @@ services: zkevm-prover: container_name: zkevm-prover - image: hermeznetwork/zkevm-prover:v2.0.1 + image: hermeznetwork/zkevm-prover:v2.0.1-hotfix.1 ports: # - 50051:50051 # Prover - 50052:50052 # Mock prover @@ -425,7 +425,7 @@ services: zkevm-permissionless-prover: container_name: zkevm-permissionless-prover - image: hermeznetwork/zkevm-prover:v2.0.1 + image: hermeznetwork/zkevm-prover:v2.0.1-hotfix.1 ports: # - 50058:50058 # Prover - 50059:50052 # Mock prover