Skip to content

Mirror zkboost from eth-act/zkboost master#377

Merged
qu0b merged 1 commit into
masterfrom
qu0b/mirror-zkboost
May 11, 2026
Merged

Mirror zkboost from eth-act/zkboost master#377
qu0b merged 1 commit into
masterfrom
qu0b/mirror-zkboost

Conversation

@qu0b
Copy link
Copy Markdown
Member

@qu0b qu0b commented May 11, 2026

Summary

  • Adds a multi-arch (amd64+arm64) build for eth-act/zkboost, published as ethpandaops/zkboost:master on every push to upstream master.
  • Uses upstream's docker/Dockerfile directly via a small zkboost/build.sh (mirrors the ere-server-zisk pattern), 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 :latest that's gated on release tags. For devnet configs we want a moving :master tag for development; this mirror provides that.

Image is tiny (~150MB on disk, ~46MB compressed) so the build is cheap on standard runners.

Test plan

  • Trigger the workflow via workflow_dispatch with defaults (eth-act/zkboost@master) and confirm ethpandaops/zkboost:master + :master-<sha> are pushed for both archs, and the manifest job assembles the multi-arch tag.

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).
@qu0b qu0b merged commit c91412c into master May 11, 2026
3 checks passed
@qu0b qu0b deleted the qu0b/mirror-zkboost branch May 11, 2026 11:29
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`.
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.

2 participants