Repository navigation
Pin the Paketo builder image used by bootBuildImage - #990
Merged
Merged
Conversation
bootBuildImage defaulted to paketobuildpacks/builder-noble-java-tiny:latest. On 2026-10-23 Paketo republished that tag as an arm64-only image, so the amd64 CI runner pulled an arm64 run image and the lifecycle failed with "exec /cnb/lifecycle/creator: exec format error", breaking every build in the repository. The versioned tags are still multi-arch. Pin the builder to the current version so a floating tag can no longer break the build. Bump the version deliberately when a newer builder is wanted. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
There was a problem hiding this comment.
🟢 Approval recommended
The single-line configuration change addresses the documented builder failure without introducing any identified blocking issues.
No open issues 🎉
What changed in this PR
This PR configures Gamma’s container-image build to use a specific Paketo builder release instead of the default latest tag, addressing the reported architecture mismatch on amd64 CI runners.
Changes:
- Pins the
bootBuildImagebuilder topaketobuildpacks/builder-noble-java-tiny:0.0.200. - Preserves the existing Java 25 configuration.
| File | Description |
|---|---|
app/build.gradle |
Pins the Paketo builder used by bootBuildImage. |
Review effort: Balanced
Member
Author
|
@Goosetaf can you take a look at this? |
Goosetaf
approved these changes
Oct 25, 2026
Goosetaf
left a comment
Goosetaf
left a comment
Member
There was a problem hiding this comment.
Sorry, should have checked this earlier.
Good 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.
Root cause
bootBuildImageinapp/build.gradledid not set a builder, so Spring Boot usedpaketobuildpacks/builder-noble-java-tiny:latest. On 2026-10-23 at 14:50 UTC Paketo republished that tag as an arm64-only image. The amd64 GitHub runner then pulled the arm64 run image and the lifecycle binary failed with:Every
Build and Testrun in the repository fails at theBuild Docker imagestep until that tag is fixed, for example 39979427066 on #989 and its rerun. Main's last green run (39934107380 at 09:44 UTC) pulled the previous amd64 digest of the same tag. The versioned tags on Docker Hub, including0.0.200pushed at the same time as the brokenlatest, are still multi-arch.What changed
builder = "paketobuildpacks/builder-noble-java-tiny:0.0.200"on thebootBuildImagetask.Pinning means a floating upstream tag can no longer break the build, and builder upgrades become a deliberate, reviewable change. There is no Dependabot or Renovate config in the repo, so the version will need an occasional manual bump.
Verification
./gradlew :app:help --task bootBuildImageconfigures the task with the pinned builder.Build Docker imagestep on this PR's CI run exercises the pin on the amd64 runner.🤖 Generated with Claude Code