fix: disable BuildKit provenance so Lambda accepts the researcher image - #43
Open
gersonazgo wants to merge 1 commit into
Open
fix: disable BuildKit provenance so Lambda accepts the researcher image#43gersonazgo wants to merge 1 commit into
gersonazgo wants to merge 1 commit into
Conversation
Since BuildKit v0.10, `docker build` attaches provenance attestations by default, which wraps the result in an OCI image index (manifest list). AWS Lambda only accepts a single manifest and rejects the push with InvalidParameterValueException. Passing --provenance=false produces a single manifest that Lambda accepts. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Problem
backend/researcher/deploy.pybuilds the researcher image withdocker build. Since BuildKit v0.10, provenance attestations are attached by default, which wraps the result in an OCI image index (manifest list) rather than a single manifest.AWS Lambda does not support that format, so
terraform applyfails right after a successful push:The build log shows the cause:
The image itself is fine — correct
linux/amd64platform, layers pushed successfully. Only the manifest format is rejected.Fix
Pass
--provenance=falsetodocker build, which produces a single manifest that Lambda accepts.Verification
Reproduced and fixed on macOS 15 (Apple Silicon) with OrbStack. After the change, the
exporting attestation manifest/exporting manifest listlines disappear,terraform applycreatesaws_lambda_function.researchersuccessfully, and the Function URL responds on/health.This affects any student on a recent Docker Desktop, OrbStack, or Colima — the default changed in BuildKit v0.10, so newer installs hit it while older ones do not.
🤖 Generated with Claude Code