Skip to content

yarn missing from the aws/codebuild/standard:7.0 image #622

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

Closed
juliannicholson opened this issue Apr 17, 2023 · 7 comments
Closed

yarn missing from the aws/codebuild/standard:7.0 image #622

juliannicholson opened this issue Apr 17, 2023 · 7 comments

Comments

@juliannicholson
Copy link

The aws/codebuild/standard:6.0 image contained yarn. However the aws/codebuild/standard:7.0 does not. This is causing our codebuild's to fail as we rely on the yarn executable.

I can see lines in the aws/codebuild/standard:6.0 dockerfile installing yarn but these aren't in aws/codebuild/standard:7.0. Please could these lines be added back in so that the container image contains yarn.

@hoegertn
Copy link

Yes, this is a big breaking change and given that e.g. AWS CDK with projen uses yarn by default this is not a great idea.

@subinataws
Copy link
Contributor

Thanks for reporting the issue. I believe yarn was taken off due to the signature expiry issue that crops up periodically. For example, #595. When the signature expires, it breaks build for everyone using the image, irrespective of whether they needed yarn or not.

We apologize for this regression in the newer images and will look to add this back at the earliest, once we address the yarn key expiration issue in a more automated manner.

@applerom
Copy link

The same (yarn is missing) is for aws/codebuild/amazonlinux2-aarch64-standard:3.0. It was in the previous version as well.

@ChronosMasterOfAllTime
Copy link

ChronosMasterOfAllTime commented May 25, 2023

Yarn is also missing from the AL2 x86_64:5.0 repo. I manually had to copy the 4.0 yarn installation lines into our buildspec in order for it to work.

EDIT: the above suggestion is not the best way to workaround this issue.

Running npm install -g yarn is as effective, and will net the same result.

NOTE: this is only for yarn 1.x. Please follow the 2.x+ docs for 2.x installation via corepack.

@ChronosMasterOfAllTime
Copy link

#657 Should resolve this.

@leoherran-aws
Copy link
Member

@ChronosMasterOfAllTime
Copy link

Fixed in the latest release 3228c52#diff-c1ea454e65b48efad7d52406144e50f8459244517f0eb25a5ec3da4f865a3129

@leoherran-aws my proposed solution in #657 is much simpler and doesn't require yum and/or GPG key pulls. It also is the recommended method to install per the Yarn V1 docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants