No longer able to use "n 18.16.0" in build using aws/codebuild/amazonlinux2-x86_64-standard:5.0

[neueda-randerson]

Describe the bug Since the latest release we now get an error with aws/codebuild/amazonlinux2-x86_64-standard:5.0, whereby "n 18.16.0" no longer works

To Reproduce Run the build.

Get this error:

[Container] 2023/11/14 12:35:59.822533 Running command node --version v18.18.2   [Container] 2023/11/14 12:35:59.849093 Running command n 18.16.0 /codebuild/output/tmp/script.sh: line 4: n: command not found

Expected behavior Node should switch to v18.16.0 as previously:

[Container] 2023/11/10 11:23:52.445996 Running command node --version v18.16.0

[Container] 2023/11/10 11:23:52.456745 Running command n 18.16.0 copying : node/18.16.0 installed : v18.16.0 (with npm 9.5.1)

Logs As above

Platform (please complete the following information): amazonlinux2-x86_64-standard:5.0

Additional context Add any other context about the problem here.

[joshlang]

Unable to use n 18 or n 16 or any n command any longer.

It broke randomly without any changes yesterday.

Rerunning a previously succeeded pipeline now fails.

[Container] 2023/11/14 15:25:46.342564 Entering phase BUILD
--
32 | [Container] 2023/11/14 15:25:46.343123 Running command n 18
33 | /codebuild/output/tmp/script.sh: line 4: n: command not found
34 |  
35 | [Container] 2023/11/14 15:25:46.349184 Command did not exit successfully n 18 exit status 127
36 | [Container] 2023/11/14 15:25:46.353527 Phase complete: BUILD State: FAILED

[jamieavins]

We are in the same boat...

`

[Container] 2023/11/14 15:16:10.200455 Running command n 18.16.0 -- 24 | /codebuild/output/tmp/script.sh: line 4: n: command not found 25 |   26 | [Container] 2023/11/14 15:16:10.282668 Command did not exit successfully n 18.16.0 exit status 127 27 | [Container] 2023/11/14 15:16:10.286950 Phase complete: INSTALL State: FAILED

`

[jedkass]

+1

[jonnysooter]

This is an unexpected issue from CodeBuild and we are reverting the change that caused the issue.

[jonnysooter]

Thank you for opening this issue, it is resolved now. Please try running your builds again.

[johan-seesaw]

We had to fix to aws/codebuild/amazonlinux2-x86_64-standard:5.0-23.07.28 for a bit. I'll update it back to default since you've now marked it as fixed.

[tgpfeiffer]

Thanks for taking care of this, @jonnysooter

I am wondering,

• according to https://gallery.ecr.aws/codebuild/amazonlinux2-x86_64-standard the 5.0 image was released "11 days ago" (that would be 2023-11-04), why did this problem only appear in CodeBuild on 2023-11-14?

• as for @johan-sesaw, we worked around the problem yesterday by pinning the image version to 5.0-23.07.28, but honestly speaking it's a bit difficult to investigate/debug image versions if the latest version called 5.0 is a moving target and apparently there is no fixed tag for the latest version. For example, even after your fix, https://gallery.ecr.aws/codebuild/amazonlinux2-x86_64-standard still looks like and it's hard to understand which "5.0" is the one with the defect, which "5.0" has the fix, and which of those "5.0"s is the one running in CodeBuild as "latest".

  Would it be possible to also give the latest version a tag and upload it to the public ECR and/or display the concrete version used as the latest one in CodeBuild? (Sorry, fairly unrelated to this repository.)

[jonnysooter]

We did not publish an image with this defect, so it's not available to use in ECR. The image versions you see listed are safe to use. The 5.0 image is our latest image and is defect free.

[kyptov]

2 days ago my pipelines started to fail. No updates, no issues. It was very strange. I added npm install -g n to solve the issue. Yesterday it started to fail again. Found this issue, reverted all buildspecs.

The question is, where I can view releases or updates?