Skip to content

fix(dogfood/coder): refresh apt keyrings and rename google-cloud-sdk - #29279

Merged
ethanndickson merged 1 commit into
mainfrom
dogfood-build-xcs3
Sep 14, 2026
Merged

ethanndickson merged 1 commit into
mainfrom
dogfood-build-xcs3

Conversation

@ethanndickson

@ethanndickson ethanndickson commented Sep 14, 2026 •

Copy link
Copy Markdown
Member

The dogfood base image has been failing to build on main since the 11th, on both the 22.04 and 26.04 legs: https://github.com/coder/coder/actions/runs/34796906035

Err:3 https://apt.releases.hashicorp.com jammy InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FC9CA96ACA026560
E: The repository 'https://apt.releases.hashicorp.com jammy InRelease' is not signed.

HashiCorp started signing their apt repo with a new key on the 9th. The hashicorp.gpg we ship only has the 2023 key, and as far as I can tell it hasn't been refreshed since it was first added. To fix, we'll just re-run update-keys.sh in both distro directories. This also picks up newer github-cli.gpg and google-cloud.gpg keyrings, neither of which were actually failing.

It turns out that was masking a second failure, as apt-get update was aborting the RUN before apt-get install ever ran. Google no longer publishes google-cloud-sdk (or google-cloud-sdk-datastore-emulator) in the cloud-sdk suite; they're now google-cloud-cli and google-cloud-cli-datastore-emulator. So, we'll rename them in both Dockerfile.base files, and in preferences.d/google-cloud, which pins everything from that repo to priority 1 unless allowlisted by name.

The dogfood base image build has failed on main since 2026-09-11 on
both the 22.04 and 26.04 legs. Two independent upstream changes are
responsible.

HashiCorp now signs apt.releases.hashicorp.com with a new key
(FC9CA96ACA026560, created 2026-09-09). The checked-in hashicorp.gpg
only held the 2023 key (AA16FCBCA621E701), so apt-get update failed
with NO_PUBKEY. Running update-keys.sh in both distro directories
picks up the new key. It also refreshes github-cli.gpg and
google-cloud.gpg, which had drifted upstream but were not failing.

Google has stopped publishing google-cloud-sdk and
google-cloud-sdk-datastore-emulator in the cloud-sdk suite; the
packages are now google-cloud-cli and
google-cloud-cli-datastore-emulator. apt-get install failed with
"no installation candidate" once the key problem was fixed. Rename
the packages in both Dockerfile.base files and in
preferences.d/google-cloud, whose allowlist pins would otherwise
leave the new names at priority 1.
@ethanndickson
ethanndickson marked this pull request as ready for review September 14, 2026 07:00
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 14, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-14T07:03:58.596080Z 0d863f5 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@ethanndickson
ethanndickson merged commit 32bde78 into main Sep 14, 2026
60 of 61 checks passed
@ethanndickson
ethanndickson deleted the dogfood-build-xcs3 branch September 14, 2026 07:17
@github-actions github-actions Bot locked and limited conversation to collaborators Sep 14, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants