search

aws / aws-codebuild-docker-images

Official AWS CodeBuild repository for managed Docker images http://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref.html
Other
1.12k stars 977 forks source link

Broken apt repo for chrome #477

Open dbirks opened 3 years ago

dbirks commented 3 years ago

Describe the bug When running apt update in the current Ubuntu standard:5.0 image, I get an inconsistent error about the Google Chrome apt repo. I get either one of these errors:

E: The repository 'http://dl.google.com/linux/chrome/deb stable Release' does not have a Release file.

or

E: The repository 'http://dl.google.com/linux/chrome/deb stable Release' is not signed.

To Reproduce Steps to reproduce the behavior:

  1. Start a CodeBuild job with the current ubuntu standard:5.0 image
  2. Run apt update in the buildspec
  3. Hold its hand as it dies

Expected behavior It should update apt without erroring.

Logs

E: The repository 'http://dl.google.com/linux/chrome/deb stable Release' does not have a Release file.
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
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

or

E: The repository 'http://dl.google.com/linux/chrome/deb stable Release' is not signed.
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
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

Platform (please complete the following information):

Additional context I can workaround it with:

rm -f /etc/apt/sources.list.d/google-chrome.list
KyleThen commented 3 years ago

@dbirks I was having this issue this morning as well. Seems like it's working now?

dbirks commented 3 years ago

Yes same here, with the workaround removed, I just get some warnings:

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
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

I should probably keep this open for now, just so the duplicate chrome repo gets looked at.