Repository navigation
Run bin/run.sh as the Docker entrypoint - #189
Merged
Merged
Conversation
The .dockerignore file keeps only bin/run.sh from the bin folder, so bin/analyze.sh is missing from the image and every container fails to start. bin/run.sh runs the same command, and it is the entrypoint used by the other Exercism tools. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SleeplessByte
approved these changes
Nov 17, 2026
SleeplessByte
left a comment
Member
There was a problem hiding this comment.
Now blame who made the earlier change 👀
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.
This PR was opened by Claude, an AI assistant working on iHiD's behalf.
What was broken
Every analyzer job in production fails. The tooling invoker logs each one as status 513 after about half a second, and students get no analysis. The invoker's logs go back 3.5 days, and every job in that period failed.
The Dockerfile sets
ENTRYPOINT ["/opt/analyzer/bin/analyze.sh"], but.dockerignoreexcludesbin/except forbin/run.sh. Since #152 (November 2023),analyze.shhas been missing from the image, so Docker can't start the container.Evidence
A production job saved this error:
The production image has
/opt/analyzer/bin/run.shand nothing else inbin. Buildingmainlocally and running it gives the same error, with exit code 127. The smoke tests don't catch this, becausebin/run-tests-in-docker.shreplaces the entrypoint withbin/run-tests.sh.Fix
This PR points the entrypoint at
/opt/analyzer/bin/run.sh. That script runs the same command asanalyze.sh(node ./dist/analyze.js "$@"), and the other Exercism analyzers use it as their entrypoint.Verification
/mnt/exercism-iteration, the argumentspizza-order /mnt/exercism-iteration/ /mnt/exercism-iteration/, with--network none --read-only. I used thetest/fixtures/pizza-order/exemplarfixture. The container exited with 0, and theanalysis.jsonit wrote matchesexpected_analysis.json.bin/run-tests-in-docker.shpasses.After merging
The Deploy workflow will build the image and push it to ECR with the
productiontag, which the tooling invoker runs. Analyzer jobs should then succeed.🤖 Generated with Claude Code