Repository navigation
fix(ci): seed image smoke config through Docker volume - #23
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
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.
Change
Seed private smoke configuration through an owned Docker volume using docker cp and a disposable helper. Remove host chown and bind-mount dependence from the non-root DinD runner; clean up both containers and the volume.
Verification
Executed the exact workflow shell as host UID1000 against the production image built by main CI 43488659445. Authenticated readiness and MCP list passed; wrong source, missing bearer and invalid MCP credential were rejected. Runtime remains UID1000 with a read-only root, dropped capabilities and no-new-privileges.
The image build is fixed by merged infrastructure PR1778. No release or runtime promotion has happened; a successful exact-main CI including the hardened smoke and signing is still required.