Unsupported Manifest/Layer Media type error

[corbinabeebe]

Hi All,

I received the following error:

Stack | 7:59:50 PM | CREATE_FAILED        | AWS::Lambda::Function                         | Nextjs/NextjsAssetsDeployment/Fn (NextjsNextjsAssetsDeploymentFn8972AAE9) 
Resource handler returned message: "The image manifest or layer media type for the source image XXXXX.dkr.ecr.us-west-2.amazonaws.com/cdk-XXXXX-container-assets-XXXXX-region:adksdlksaldsl is not supported. 
(Service: Lambda, Status Code: 400, Request ID: XXX)" (RequestToken: , HandlerErrorCode: InvalidRequest)

has anyone ran into this issue and what are the possible workarounds?

From what I can tell by the error, the Assets deployment Lambda function doesnt like the project image for some reason, do I need to build my image differently?
It would seem the image asset is not supported most likely, it looks like I can pass in my own dockerfile:
with add something like this:

          nextjsContainersProps:{
            dockerImageAsset: new aws_ecr_assets.DockerImageAsset(this, 'Image', {
              assetName: assetName, 
              directory: buildPath,
              buildSecrets: props.buildSecrets,
              }),
          },

Additionally, Is there a way I can define what ecr repo the image uploads too so I am not using the defualt repo for cdk?

Thanks!

[coltenkrauter]

I have not faced this...

Can you share your Dockerfile? The issue might be related to:

1. Base Image: Lambda works best with Lambda-compatible base images, like amazon/aws-lambda-nodejs:22.
2. Platform: If you're using a custom image, ensure it's built for linux/amd64.

Example with platform specified:

new aws_ecr_assets.DockerImageAsset(this, 'CustomImage', {
    directory: './path-to-dockerfile',
    platform: 'linux/amd64',
});

[StuClift]

Lambda doesn't like the manifest docker produces. Consider setting https://docs.docker.com/build/building/variables/#buildx_no_default_attestations to true.

[coltenkrauter]

Ah I see. By chance, is your code in public repositories that you can share? I'd love to take a look.

Any way you can share a bit more of the code might help in debugging. Meanwhile, @bestickley may have an idea of why you are experiencing this.

[corbinabeebe]

Ah I see. By chance, is your code in public repositories that you can share? I'd love to take a look.

Any way you can share a bit more of the code might help in debugging. Meanwhile, @bestickley may have an idea of why you are experiencing this.

@coltenkrauter I can share more of the code but not the entire repo. Anything in particular you would like me to share?

[corbinabeebe]

Lambda doesn't like the manifest docker produces. Consider setting https://docs.docker.com/build/building/variables/#buildx_no_default_attestations to false.

How do I pass the arg in if I am not using a custom image asset?

[StuClift]

How do I pass the arg in if I am not using a custom image asset?

BUILDX_NO_DEFAULT_ATTESTATIONS=1 npm cdk deploy

[bestickley]

@corbinabeebe , have you seen this? It offers some troubleshooting steps: https://repost.aws/questions/QUA20KN_o0SfOchiGO573GHw/cannot-deploy-docker-container-to-lambda

I've never seen that error.

Additionally, Is there a way I can define what ecr repo the image uploads too so I am not using the defualt repo for cdk?

I haven't verified by this is what Amazon Q says:

Yes, you can customize the ECR repository name in your CDK code. For your NextjsRegionalContainers setup, you can specify this in the overrides:

const nextjs = new NextjsRegionalContainers(this, "Nextjs", {
  healthCheckPath: "/api/health",
  buildContext: fileURLToPath(new URL("..", import.meta.url)),
  overrides: {
    nextjsRegionalContainers: {
      nextjsBuildProps: {
        builderImageProps: {
          // Specify custom ECR repository name
          repositoryName: 'my-custom-repo-name',
          // ... your other settings ...
          exclude: [
            "**/node_modules",
            "**/.next",
            "global-containers",
            "global-functions",
            "regional-containers",
            "shared",
            "*.md",
          ],
        },
      },
    },
    // ... rest of your overrides ...
  },
  relativePathToWorkspace: "./app-playground",
});

Copy

Insert at cursor
typescript
Alternatively, if you want more control over the ECR repository, you can create it explicitly and then reference it:

import * as ecr from 'aws-cdk-lib/aws-ecr';

// In your stack:
const repository = new ecr.Repository(this, 'MyEcrRepo', {
  repositoryName: 'my-custom-repo-name',
  // Optional: Add lifecycle rules
  lifecycleRules: [
    {
      maxImageCount: 5,  // Keep only 5 images
      description: 'Only keep 5 images'
    }
  ],
  // Optional: Add removal policy
  removalPolicy: RemovalPolicy.DESTROY  // Be careful with this in production
});

const nextjs = new NextjsRegionalContainers(this, "Nextjs", {
  // ... other config ...
  overrides: {
    nextjsRegionalContainers: {
      nextjsBuildProps: {
        builderImageProps: {
          repository: repository,
          // ... other builder props ...
        },
      },
    },
  },
});

Copy

Insert at cursor
typescript
This gives you more control over the ECR repository configuration, including:

Custom repository name

Lifecycle rules

Image tag mutability

Image scanning configuration

Removal policies

Remember that if you're using a custom repository name, ensure you have the necessary IAM permissions set up correctly for pushing and pulling images from this repository.

[bestickley]

Marking this as answer for house keeping purposes. Please let me know if this doesn't address your issue.