fix: drop --archiver flag removed in v5.0.0#53
Merged
Conversation
The archiver is now embedded in --node and is no longer a separate CLI flag. Passing --archiver causes the node to fail on startup with v5.
alexghr
approved these changes
Jul 14, 2026
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
2 participants
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
The
--archiverCLI flag was removed in Aztec v5.0.0 — the archiver is now embedded in--node. Passing--archivercauses the node to fail on startup.This fixes the entrypoint to work with the v5.0.0 image from PR #52.
Changes
--archiverfrom the startup flags insequencer/entrypoint.shReference
aztec start --archiver/--pxeflags removed (both are embedded in the node)."