Move Docker images off EOL bullseye and onto current versions - #9490
Merged
Merged
Conversation
Bullseye is EOL, so move both rails stages to bookworm, take node from 20 to 22, swap the deprecated apt-key call for a keyring file, and pin the nginx and anycable-go images rather than tracking latest. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01549BYfDEpyce9GLgGnJqpm
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
1 participant
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.
Follow-up to #9489, which only silenced the expired-metadata error. This moves
the images onto supported versions so the workaround is no longer needed.
ruby:3.4.4-bullseye→ruby:3.4.4-bookwormin both stages. Bullseye is EOL;bookworm is the current stable. The Ruby patch level is deliberately unchanged
so this stays a base-OS change: bumping 3.4.4 → 3.4.10 also means updating
.ruby-version, theGemfilepin and everyone's local install, which belongsin its own PR.
apt-key addfor the yarn repo with a keyring file,matching how the nodesource repo is already set up.
apt-keyis gone intrixie, so this is needed before any further base bump.
nginx→nginx:1.31.2andanycable/anycable-go→anycable/anycable-go:1.6.16instead of tracking floatinglatesttags.Verified locally: the apt stage builds on bookworm and installs node 22.23.2,
yarn 1.22.22, cmake, graphicsmagick and libvips42. The full image build happens
in the deployer.
🤖 Generated with Claude Code
https://claude.ai/code/session_01549BYfDEpyce9GLgGnJqpm