Skip to content

fix: add base-consensus binary to geth and nethermind Dockerfiles#1017

Open
Sertug17 wants to merge 1 commit intobase:mainfrom
Sertug17:fix/add-base-consensus-to-geth-nethermind
Open

fix: add base-consensus binary to geth and nethermind Dockerfiles#1017
Sertug17 wants to merge 1 commit intobase:mainfrom
Sertug17:fix/add-base-consensus-to-geth-nethermind

Conversation

@Sertug17
Copy link
Copy Markdown

Fixes #1016

reth/Dockerfile already includes the base-consensus binary, but geth/Dockerfile and nethermind/Dockerfile were missing it entirely.

Operators using geth or nethermind with USE_BASE_CONSENSUS=true would get "Base client is not supported for this node type" error and fail to start — potentially missing the April 20th Base V1 Sepolia upgrade deadline.

Changes:

  • Added Rust builder stage to both Dockerfiles
  • Added base-consensus binary copy from builder
  • Added base-consensus-entrypoint copy

@cb-heimdall
Copy link
Copy Markdown
Collaborator

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
Sum 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

base-consensus binary missing from geth and nethermind Dockerfiles

2 participants