Add Docker smoke test running init command in CI#770
Merged
Conversation
cyc60
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
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
Adds a smoke test to the Docker CI workflow to verify the built container image is functional beyond just building successfully.
Details
In the per-platform
dockerjob, after the push-by-digest build:load: true(reusing the GHA cache, so effectively free) and tags itoperator-smoke-test:ciso it can be run locally on the runner.initcommand inside the container.initexercises the CLI wiring and Python startup without needing execution/consensus RPC endpoints, so it runs offline and exits0on success.--no-verifyskips the interactive mnemonic verification that would otherwise block on stdin.If the container fails to start or the CLI is broken,
docker runreturns non-zero and the step (and job) fails.