aws-solutions / aws-control-tower-customizations

The Customizations for AWS Control Tower solution combines AWS Control Tower and other highly-available, trusted AWS services to help customers more quickly set up a secure, multi-account AWS environment using AWS best practices.
https://docs.aws.amazon.com/controltower/latest/userguide/cfct-overview.html
Apache License 2.0
355 stars 205 forks source link

Package Update fails inside the buildspec install phase #147

Closed cadm-markus-brune closed 1 year ago

cadm-markus-brune commented 1 year ago
Describe the bug The build steps throw these errors:   2023-01-25T07:04:35.642+01:00 [Container] 2023/01/25 06:04:31 Running command apt-get -q update 1> /dev/null
  2023-01-25T07:04:41.796+01:00 W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1
  2023-01-25T07:04:41.796+01:00 W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1
  2023-01-25T07:04:41.796+01:00 W: GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging yarn@dan.cx
  2023-01-25T07:04:41.796+01:00 E: The repository 'https://dl.yarnpkg.com/debian stable InRelease' is not signed.
  2023-01-25T07:04:41.796+01:00 W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1
  2023-01-25T07:04:41.796+01:00 W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:3 and /etc/apt/sources.list.d/google.list:1

To Reproduce Each time the pipeline runs.

Expected behavior The package update should run without problems

Solution Added the following line

Please complete the following information about the solution:

balltrev commented 1 year ago

I believe this issue is a duplicate of https://github.com/aws-solutions/aws-control-tower-customizations/issues/144 and has been resolved by the AWS CodeBuild team.