Pipeline broken due to Kernel Version

Describe the bug The pipeline is current broken at the build stage due to a Kernel Version error:

Unpacking libc6-dev:amd64 (2.27-3ubuntu1.5) over (2.27-3ubuntu1.4) ...
--
250 | Preparing to unpack .../libc-dev-bin_2.27-3ubuntu1.5_amd64.deb ...
251 | Unpacking libc-dev-bin (2.27-3ubuntu1.5) over (2.27-3ubuntu1.4) ...
252 | Preparing to unpack .../linux-libc-dev_4.15.0-169.177_amd64.deb ...
253 | Unpacking linux-libc-dev:amd64 (4.15.0-169.177) over (4.15.0-151.157) ...
254 | Preparing to unpack .../libc6_2.27-3ubuntu1.5_amd64.deb ...
255 | ERROR: Your kernel version indicates a revision number
256 | of 255 or greater.  Glibc has a number of built in
257 | assumptions that this revision number is less than 255.
258 | If you\'ve built your own kernel, please make sure that any
259 | custom version numbers are appended to the upstream
260 | kernel number with a dash or some other delimiter.
261 |  
262 | dpkg: error processing archive /var/cache/apt/archives/libc6_2.27-3ubuntu1.5_amd64.deb (--unpack):
263 | new libc6:amd64 package pre-installation script subprocess returned error exit status 1
264 | Errors were encountered while processing:
265 | /var/cache/apt/archives/libc6_2.27-3ubuntu1.5_amd64.deb
266 | E: Sub-process /usr/bin/dpkg returned an error code (1)
267 |  
268 | [Container] 2022/03/01 22:45:46 Command did not exit successfully apt-get update && apt-get upgrade -y exit status 100
269 | [Container] 2022/03/01 22:45:46 Phase complete: INSTALL State: FAILED
270 | [Container] 2022/03/01 22:45:46 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: apt-get update && apt-get upgrade -y. Reason: exit status 100

To Reproduce Just run the pipeline using the defaults that AWS providers.

Expected behavior The dependencies step should at least pass no problem

Please complete the following information about the solution:

• [2.2.0] Version
• [us-west-2] Region
• [No] Was the solution modified from the version published on this repository?
• If the answer to the previous question was yes, are the changes available on GitHub?
• [Yes] Have you checked your service quotas for the sevices this solution uses?
• [Yes] Were there any errors in the CloudWatch Logs?

Screenshots N/A

Additional context I tried changing the image used in the Codebuild to: aws/codebuild/standard:5.0 and also a non-latest version of aws/codebuild/standard:4.0 and no luck.

[stumins]

The CodeBuild team has released a fix that should resolve this. Please reopen this issue if you continue to experience this problem.

[stumins]

We are aware of this issue and are working with the AWS CodeBuild team to resolve the issue upstream. AWS CodeBuild is actively working on a fix and we do not expect needing to patch CFCT as part of the resolution.

As mentioned above, not upgrading libc6 at runtime by adding sudo apt-mark hold libc6* before apt-get upgrade in buildspec stages should work if you require an immediate workaround.

We will provide additional details as we receive more information. Thank you for your patience.