Repository navigation
fix: validate Docker setup and entry points - #26
Merged
Merged
Conversation
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.
Make the Docker scripts locate the checkout from their own paths, use a portable Bash entry point, and open the mounted repository as the working directory. Limit the build context to docker/, document the ephemeral shell container, and provide Python, the pinned compiler components, and executable PATH. Separate compiler and coverage-tool installation layers.
Validation: image build and both scripts passed from outside the checkout. On Linux ARM64 in Docker, workspace build, all four tool installations, CLI help, and the minimal offline pipeline passed. The full Linux CI suite also passed. No model service was called.