feat(v2): Migrate Debian base from Bookworm to Trixie with backward-compatible tags #28
Conversation
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
added 7 commits
October 21, 2025 20:32
…ompatible tags - Update Dockerfile.v2 to use Debian trixie as base OS - Update library packages for trixie (including t64 time64 transition libs) - Support both trixie and bookworm BASEOS values for smooth transition - Update docker-ci.yml and docker-image.v2.yml matrices to build v2 on trixie - v1 images remain on bookworm (no change) - Add automatic bookworm tag aliasing for v2 trixie-built images - Also add bullseye compatibility tags for maximum backward compatibility This provides users pulling :bookworm tags with the latest trixie-built images while maintaining tag continuity. The same digest is served for both :trixie and :bookworm tags on v2 images.
- Update README with Trixie migration notice and base OS clarification - Add detailed migration guide section in docs/migration.md - Create CHANGELOG.md with unreleased Trixie migration entry - Document tag mapping (trixie/bookworm/bullseye compatibility) - Add library version comparison table (t64 time64 updates) - Include testing checklist, rollback plan, and FAQ - Clarify v1 vs v2 base OS differences
Remove the static CHANGELOG.md to avoid duplication; rely on git history, release notes, and existing docs for change tracking.
…s, table spacing)
…agickwand, libtidy, libzip, libavif, libicu)
…to avoid install failures
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.
Summary
This PR migrates v2 Debian-based images from Debian Bookworm to Debian Trixie, aligning with upstream PHP official images while maintaining complete backward compatibility through tag aliasing.
What Changed
v2 Images (with
-v2suffix):bookwormtags continue to work as aliases (point to same Trixie image):bullseyetags also aliased for legacy compatibilityt64packages)v1 Images (without
-v2suffix)Alpine Images
Why This Change?
:bookwormtags work transparentlyBackward Compatibility
Users pulling
:bookworm-v2tags will automatically receive Trixie-built images with identical behavior. The same digest is served for:8.3-fpm-trixie-v2(new explicit tag)8.3-fpm-bookworm-v2(compatibility alias)8.3-fpm-bullseye-v2(legacy alias)No action required for users currently using
:bookworm-v2tags.Technical Changes
Dockerfile Updates
Dockerfile.v2to handle both Trixie and BookwormBASEOSvaluest64suffix):libpng16-16t64,libmagickwand-6.q16-7t64,libvips42t64libavif16t64,libmemcached11t64,libsnmp40t64CI/Workflow Updates
docker-ci.yml: v2 matrix now builds ontrixieinstead ofbookwormdocker-image.v2.yml: matrix updated to usetrixiebasedocker buildx imagetools createstep to publish:bookwormcompatibility tagsDocumentation
docs/migration.mdCHANGELOG.mdwith detailed migration notesTesting Plan
Pre-Merge (Canary)
Post-Merge
Rollback Plan
If issues arise:
Related Documentation
Checklist
Review Focus Areas:
t64suffixes)