Closed andreineculau closed 2 months ago
Is there another keyring we can get that isn't expired?
PS: Maybe someone can explain why do we need github cli on the homebrew docker image.
Homebrew CI makes heavy use of gh
.
Can it be removed?
Not without breaking pretty much all of our CI.
See also https://github.com/cli/cli/issues/9569.
Seems like the image just needs to be rebuilt. If this is blocking you, consider using ghcr.io/homebrew/ubuntu22.04:master
instead.
A rebuilt :latest
image should be available on the next brew
tag (likely early next week).
In a pinch, you could probably also run this inside the :latest
container:
curl -fsSL https://cli.github.com/packages/githubcli-archive-keyring.gpg |
sudo dd of=/usr/share/keyrings/githubcli-archive-keyring.gpg
Hi folks, many apologies for the troubles from the GitHub CLI.
I just added some docker related details to our tracking issue: https://github.com/cli/cli/issues/9569#docker-build-failing
I can confirm the new keyring is available at https://cli.github.com/packages/githubcli-archive-keyring.gpg. If you own the layer that grabs this key, I would expect rebuilding the image solves the problem. If you don't own the layer, running:
RUN wget -qO- https://cli.github.com/packages/githubcli-archive-keyring.gpg | sudo tee /etc/apt/keyrings/githubcli-archive-keyring.gpg > /dev/null \
&& chmod go+r /etc/apt/keyrings/githubcli-archive-keyring.gpg
Before the apt update
, should workaround until the base layer is updated.
Sorry 🙏
@williammartin thanks for chiming in!
I think /etc/apt/keyrings
there should be /usr/share/keyrings
, because our Dockerfile
still uses the old instructions:
https://github.com/Homebrew/brew/blob/94eb0c7f83a8f085d7d08ffcedd06855a0da7918/Dockerfile#L47-L51
I'll open a PR to update our Dockerfile
.
Ahha! Thanks. I'm going to update our issue to provide both sets of instructions.
Thank you @carlocab ! We're good on our side. We have a hotfix to remove everything gh (via apt; we also make use of gh, but we install it via homebrew 😅 #inception)
And thank you @williammartin ! Do take it easy and enjoy the weekend! ❤️
Updated the instructions to account for the old location here: https://github.com/cli/cli/issues/9569#what-do-you-need-to-do-about-apt
Cheers!
Thanks @williammartin! Dockerfile
now updated in #18272.
This should be fixed as of https://github.com/Homebrew/brew/releases/tag/4.3.20.
brew doctor
outputVerification
brew doctor
output" above saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
twice and am still able to reproduce my issue.brew install wget
. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.brew config
outputWhat were you trying to do (and why)?
use the latest homebrew docker image and get the latest aptitude packages
In https://github.com/Homebrew/brew/blob/94eb0c7f83a8f085d7d08ffcedd06855a0da7918/Dockerfile#L47 we get the github cli keyring, but it expired.
so running
Followed by an apt-get update, like
will now error.
Any other fix than build a new image or rebuild the current image (same version)? For the time being, I guess it can be fixed downstream by updating the keyring.
PS: Maybe someone can explain why do we need github cli on the homebrew docker image. Can it be removed?
What happened (include all command output)?
What did you expect to happen?
no error
Step-by-step reproduction instructions (by running
brew
commands)