-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CDK Deployment crashes: Dockerfile aws-lambda-nodejs/lib/Dockerfile has unsupported version of NodeJs 14 for new pnpm version #24820
Comments
Having the same issue |
It should/might work if you explicitly specify the SAM base image version to use version 16 like: dockerImage: DockerImage.fromRegistry('public.ecr.aws/sam/build-nodejs16.x:latest'), |
Also taking our pipelines down. |
same here |
Welcome in a club |
We just merged a fix to this today #24821. We are working on getting this released. |
in my case I was able to solve this by changing any places where we were using |
I have the same issue: const dockerImageAsset = new ecrAssets.DockerImageAsset(
this,
StringFormatter.formatId("nest-app-docker-image"),
{
directory: path.join(__dirname, "../.."),
platform: ecrAssets.Platform.LINUX_AMD64,
}
); My docker file is like this: FROM node:16-slim My CDK version is: 2.55.0 (build 077d77d) [edit] I also updated my package version from Any idea? |
In my case, the problem was solved by specifically setting the runtime in the NodeJSFunction to |
Try this one - https://dev.to/airmonitor/aws-cdk-arm64-codebuild-is-broken-2e9a what you should change is the build_image=codebuild.LinuxBuildImage.AMAZON_LINUX_2_ARM_2 to x86_64 if you would like, but the pipeline has been changed to enforce node 16 everywhere. |
Same here! Thank you. |
This should have been fixed with |
Yes, this is still valid for ARM64 builds, the AMAZON_LINUX_2_ARM_2 build image only has node12 (because AWS didn't provide timely support for installing something more up-to-date). |
@airmonitor I think your issue might be something else. This issue is specific to the It sounds like you are talking about CDK in general not supporting nodejs 12? |
This is how i got it mine fixed. Just upgrade to said version and re-deploy with no extra headaches |
|
Hi there,
it is unfortunately not possible to deploy aws cdk chages since today.
pnpm dependency was updated today to the latest version v8. (GithubV8ReleaseLink)
pnpm v8 is not compatible with Node.js v. 14 (see https://pnpm.io/installation#compatibility)
The dockerfile aws-lambda-nodejs/lib/Dockerfile uses image: ARG IMAGE=public.ecr.aws/sam/build-nodejs14.x
Expected Behavior
Deployment should be completed without error code
Current Behavior
Error: Process completed with exit code 1. CI/CD pipeline is down.
Reproduction Steps
Logs:
Possible Solution
Please update public.ecr.aws/sam/build-nodejs14.x:latest into v16.4.
Additional Information/Context
No response
CDK CLI Version
2.70.0
Framework Version
No response
Node.js Version
v18.13.0
OS
macOs
Language
Typescript
Language Version
Version 5.0.2
Other information
No response
The text was updated successfully, but these errors were encountered: