fix(docker): add --provenance=false --sbom=false for Lambda compatibility
Docker BuildKit (especially with docker-container driver) may create OCI image manifests with attestations that AWS Lambda does not support. Lambda requires Docker V2 Schema 2 format without multi-manifest index. This fix ensures the build script generates Lambda-compatible images regardless of the user's Docker/BuildKit configuration. Fixes #206
This commit is contained in:
@@ -78,7 +78,19 @@ build_and_push_image() {
|
|||||||
echo "Building $IMAGE_NAME:$TAG..."
|
echo "Building $IMAGE_NAME:$TAG..."
|
||||||
|
|
||||||
# Build Docker image
|
# Build Docker image
|
||||||
docker buildx build --platform linux/$ARCH -t $IMAGE_NAME:$TAG -f $DOCKERFILE_PATH --load ../src/
|
# Note: --provenance=false and --sbom=false are required for Lambda compatibility
|
||||||
|
# Without these flags, Docker BuildKit (especially with docker-container driver) may create
|
||||||
|
# OCI image manifests with attestations that AWS Lambda does not support.
|
||||||
|
# Lambda requires Docker V2 Schema 2 format without multi-manifest index.
|
||||||
|
# See: https://github.com/aws-samples/bedrock-access-gateway/issues/206
|
||||||
|
docker buildx build \
|
||||||
|
--platform linux/$ARCH \
|
||||||
|
--provenance=false \
|
||||||
|
--sbom=false \
|
||||||
|
-t $IMAGE_NAME:$TAG \
|
||||||
|
-f $DOCKERFILE_PATH \
|
||||||
|
--load \
|
||||||
|
../src/
|
||||||
|
|
||||||
# Get the account ID
|
# Get the account ID
|
||||||
ACCOUNT_ID=$(aws sts get-caller-identity --region $REGION --query Account --output text)
|
ACCOUNT_ID=$(aws sts get-caller-identity --region $REGION --query Account --output text)
|
||||||
|
|||||||
Reference in New Issue
Block a user