Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #2278
I have not found a better solution to keep the gpg keys updated/rotated automatically.
The gpg keys from the current release are valid until 2026, but with PR it ensures older Docker images of the clab-devcontainer can still function correctly even if the GPG key for the GitHub CLI repository has expired. The goal is to make the container update the GPG key as needed without requiring users to rebuild the image or manually intervene, allowing apt update to succeed seamlessly.
By configuring apt to run /usr/local/bin/update-github-cli-key.sh before any update operation, its ensure that the GPG key is refreshed every time apt update is invoked. This happens automatically and does not require any manual intervention from the user.
If the key installed in the image is expired, the script will fetch the latest key from the GitHub servers, updating the keyring so that apt can verify the repository signatures correctly.