-
Notifications
You must be signed in to change notification settings - Fork 982
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
Invalid signature from cli.github.com #739
Comments
Hi folks, many apologies for the troubles from the GitHub CLI. Glancing around this repo I believe that the important layer that needs to be rebuilt is:
Any layer on top of this that does For anyone building their images from the ones here, the workaround is probably to add the following to your dockerfiles before running
Or possibly trimmed down as:
This will grab the new keyring. |
Thanks a lot for this @williammartin 👍 I think this affects many CodeBuild users, so I hope it also gets some eyes from the AWS side! |
If the workaround above works for you, it would be great if you could drop a note back here for others and for us to know, since we'll be trying to proactively reach out on issues for to support. 🙏 |
@williammartin I can confirm that adding However, it still should be fixed to the original image. |
Another quick and dirty workaround is to remove the repository before running
|
Hopefully the AWS folks will come bail out our embarrassment soon 😅 Thanks for the confirmation! I'll probably update the linked issue with a Docker specific section shortly. |
CodeBuild team is working on releasing a new image to resolve this issue |
CodeBuild has deployed a patch to our images to update the keyring. You will no longer see this error. Resolving this issue. |
This page actually worked for me. The "What do you need to do about it?" section. |
(type -p wget >/dev/null || (sudo apt update && sudo apt-get install wget -y)) |
Module 3 : Configurer l'AWS CLI INTRODUCTION CRÉER VOTRE COMPTE CONFIGURER LES UTILISATEURS CONFIGURER L'AWS CLI CONFIGURER L'IDE AWS CLOUD9 Qu'allez-vous accomplir ? Pour interagir avec AWS à l'aide de la CLI, nous devons configurer les informations d'identification à utiliser lors des appels d'API. Nous montrerons également comment vous pouvez configurer plusieurs profils pour accéder à plusieurs comptes AWS, soit avec des informations d'identification supplémentaires, soit par le biais d'un changement de rôle IAM. Amazon Web Services Français AWS This topic describes how to install or update the latest release of the AWS Command Line Interface (AWS CLI) on supported operating systems. For information on the latest releases of AWS CLI, see the AWS CLI version 2 Changelog on GitHub. To install a past release of the AWS CLI, see Installing past releases of the AWS CLI version 2. For uninstall instructions, see Uninstalling the AWS CLI version 2. Important Topics Il existe différentes façons d'installer l'AWS CLI, en fonction de votre système d'exploitation ou de votre préférence d'utilisation des conteneurs. Pour installer l'AWS CLI v2, consultez la section lnstalling or updating the latest version of the AWS CLI (Installation ou mise à jour de la dernière version de l'AWS CLI). Produits› Amazon Lightsail Avantages |
macOS support policy updates for the AWS CLI v2 On 2024-06-20, the AWS CLI v2 PKG installer and source distribution bundle will no longer support macOS versions 10.14 (Mojave) and prior. We may discontinue support sooner if it’s necessary to respond to an emergent security issue. Moving forward, the AWS CLI v2 will provide comööö where N is Apple’s latest major macOS version. After the AWS CLI team ends support for a specific version of macOS, compatibility with newer AWS CLI v2 versions will not be guaranteed. For example, once Apple releases macOS 15, the AWS CLI v2 will end support for macOS 10.15 (Catalina). The following table shows the supported macOS versions under the new policy: |
@DEATH-GOTHIC can you explain what issue you are experiencing? Are you running into the original reported error in this issue when running |
I think it's just spam FWIW |
Describe the bug
Cannot run
apt update
in the build image.To Reproduce
Steps to reproduce the behavior:
sudo apt-get update
in start of the buildExpected behavior
sudo apt-get update
worksPlatform (please complete the following information):
Additional context
The keys were updated because of expiration, see cli/cli#9569
The text was updated successfully, but these errors were encountered: