Skip to content

Install Chrome's apt key without apt-key (Ubuntu 26.04) - #157

Merged
marcusosterberg merged 1 commit into
mainfrom
ci/ubuntu-26
Nov 5, 2026
Merged

marcusosterberg merged 1 commit into
mainfrom
ci/ubuntu-26

Conversation

@marcusosterberg

Copy link
Copy Markdown
Contributor

GitHub moves ubuntu-latest to Ubuntu 26.04 between 2026-10-19 and 2026-11-19 (actions/runner-images#14748). Ubuntu 26.04 ships apt 3.2.0 without apt-key, so the Chrome install step, which starts with wget ... | sudo apt-key add -, fails on every run that lands there.

The key now goes to /etc/apt/keyrings/google-chrome.gpg and the source refers to it with signed-by, over https. The source is written to google-chrome.list, the file Chrome's own package uses, so the two can't end up as conflicting entries.

Changed: linux.yml, manual-start.yml

Testing

  • A temporary branch ran linux.yml on ubuntu-26.04: green, Chrome 156.0.8078.47 installed, no apt errors.
  • Same result in clean ubuntu:24.04 and ubuntu:26.04 containers.
  • The check on this PR runs on ubuntu-latest, which is 24.04 or 26.04 depending on where GitHub's rollout is.

GitHub moves ubuntu-latest to Ubuntu 26.04 between 2026-10-19 and
2026-11-19. Ubuntu 26.04 ships apt 3.2.0 without apt-key, so the
"Install latest Chrome" steps, which start with
`wget ... | sudo apt-key add -`, fail on every run that lands there.

The key now goes to /etc/apt/keyrings/google-chrome.gpg and the source
refers to it with signed-by, over https. The source is written to
google-chrome.list, the file Chrome's own package uses, so the two can't
end up as conflicting entries for the same repository.

Checked in clean ubuntu:24.04 and ubuntu:26.04 containers: apt-get
update gives no warnings and google-chrome-stable 156.0.8078.47 is the
candidate on both.

Changed (2): linux.yml manual-start.yml
@marcusosterberg
marcusosterberg merged commit 13b34ee into main Nov 5, 2026
1 check passed
@marcusosterberg
marcusosterberg deleted the ci/ubuntu-26 branch November 5, 2026 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant