From 23d92e5338fbd01521246bb1c3c987aff288bba0 Mon Sep 17 00:00:00 2001 From: erhan yasar Date: Mon, 27 Apr 2026 00:58:24 +0300 Subject: [PATCH] fix: default CLIENT to reth in docker-compose.yml README.md already documents reth as the default execution client, but docker-compose.yml used geth as the fallback value for the CLIENT variable. This meant that running docker compose up without explicitly setting CLIENT=reth would silently start geth instead of reth. After Base V1 activates (early May 2026), only base-reth-node supports the network. Having geth as the implicit default increases the risk of operators missing the migration. Changed the CLIENT fallback from geth to reth in both the execution and node service Dockerfile references so the default behaviour matches the documented default and the post-V1 requirement. Operators who intentionally run geth can still do so by setting CLIENT=geth explicitly in their env file. Fixes #1010. --- docker-compose.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docker-compose.yml b/docker-compose.yml index 83d2c4c1..9eda3317 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -2,7 +2,7 @@ services: execution: build: context: . - dockerfile: ${CLIENT:-geth}/Dockerfile + dockerfile: ${CLIENT:-reth}/Dockerfile restart: unless-stopped ports: - "8545:8545" # RPC @@ -20,7 +20,7 @@ services: node: build: context: . - dockerfile: ${CLIENT:-geth}/Dockerfile + dockerfile: ${CLIENT:-reth}/Dockerfile restart: unless-stopped depends_on: - execution