Fix Base image build#5254
Merged
Merged
Conversation
57d32f7 to
d8bad35
Compare
ViniciustCosta
approved these changes
Apr 24, 2026
Merged
javanlacerda
added a commit
that referenced
this pull request
Apr 27, 2026
That's a follow up of #5254. It moves to push the immutable images to a private folder `clusterfuzz-immutable-images` --------- Signed-off-by: Javan Lacerda <javanlacerda@google.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Title: Fix Cloud Build GPG errors and upgrade to Node.js 20 (LTS)
Summary
This PR resolves the build failures in the clusterfuzz-images project caused by missing or expired GPG keys in the legacy NodeSource installation scripts. It also upgrades the base environment to use Node.js 20 (LTS).
Problem
The existing docker/base build was failing with the following error:
GPG error: https://deb.nodesource.com/node_19.x focal InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1655A0AB68576280
This was due to the use of the deprecated setup_19.x script and a Node.js version (19) that is no longer supported.
Solution
Changes
Impact