Mirror zkboost from eth-act/zkboost master#377
Merged
Conversation
Adds a multi-arch (amd64+arm64) build for ghcr.io/eth-act/zkboost via upstream's docker/Dockerfile, published as ethpandaops/zkboost:master on every push to upstream master. Useful for devnet configs that want a moving "latest from master" tag, which upstream zkboost doesn't publish (only SHA-tagged builds and release-tagged :latest).
barnabasbusa
approved these changes
May 11, 2026
qu0b
added a commit
to qu0b/ethereum-package
that referenced
this pull request
May 11, 2026
Switch from locally-built zkboost + ghcr ere-server-zisk to the ethpandaops registry mirrors at the moving `:master` tag: zkboost ethpandaops/zkboost:master ere-server-zisk ethpandaops/ere-server-zisk:master Auto-resolution is bypassed (only the official eth-act registry triggers it), so per-zkvm `image`/`elf_url`/`program_vk_url` are set explicitly. Depends on ethpandaops/eth-client-docker-image-builder#377 to seed `ethpandaops/zkboost:master`.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ethpandaops/zkboost:masteron every push to upstream master.docker/Dockerfiledirectly via a smallzkboost/build.sh(mirrors theere-server-ziskpattern), so we don't have to keep a vendored Dockerfile in sync.Why
Upstream zkboost CI only publishes per-commit SHA-tagged images (
ghcr.io/eth-act/zkboost/zkboost:<short-sha>) and a:latestthat's gated on release tags. For devnet configs we want a moving:mastertag for development; this mirror provides that.Image is tiny (~150MB on disk, ~46MB compressed) so the build is cheap on standard runners.
Test plan
workflow_dispatchwith defaults (eth-act/zkboost@master) and confirmethpandaops/zkboost:master+:master-<sha>are pushed for both archs, and the manifest job assembles the multi-arch tag.