1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
You could create a base image that contains all your shared dependencies (i.e. codec tools) and then reference this base image in the Dockerfile on your lambda functions. The base image should be built as a pre-requisite step and pushed to an ECR repository.
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
Would you mind pointing out how exactly to create a base image and then reference it in the lambda? I was making the base image by the
DockerImageAsset
fromaws-cdk-lib/aws-ecr-assets
, and then usingasset.imageUri
to reference it when creating a lambda, like the following:But I got an Error said:
Cannot use tokens in keys or values of "buildArgs" since they are needed before deployment
.Thanks!
The error you get from CDK is because the imageUri is only known at execution time, but the buildArgs are needed at synth time. You may need to separate the build of the base image in a separate process to have the base image pushed to a known ECR registry that can then be referenced from the lambda stack. The following construct could be used to publish the base image to ECR: https://github.com/cdklabs/cdk-ecr-deployment