shunping opened a new issue, #41458:
URL: https://github.com/apache/beam/issues/41458

   ### What needs to happen?
   
   The Python SDK container images (`apache/beam_python3.X_sdk`, including ML 
images) and the Python expansion service image are built on 
`python:3.X-bookworm` (Debian 12). We should move them to `python:3.X-trixie` 
(Debian 13).
   
   **Why**
   - Smaller CVE baseline and longer support window with the current Debian 
stable.
   - Our distroless images already use `gcr.io/distroless/python3-debian13` 
(#40811). However, they copy `/usr/local` (CPython and site-packages) from the 
bookworm-based SDK image, so the distroless image currently mixes two distros. 
Moving the base image to trixie makes them consistent.
   
   **Scope**
   - `sdks/python/container/Dockerfile`: `python:${py_version}-bookworm` → 
`-trixie` (SDK and ML images, py311–py314)
   - `sdks/python/expansion-service-container/Dockerfile`: `-bookworm` → 
`-trixie`
   - `sdks/python/test-suites/direct/common.gradle`: Azure IT base image → 
`-trixie`
   - Docs: custom container examples in `environments.md` and the learning 
prompts
   - `CHANGES.md`: Breaking Changes entry
   
   **Plan:** a hard switch in a single release with a breaking-change notice. 
No dual `-bookworm` tags.
   
   **Notable changes from bookworm to trixie**
   - glibc 2.36 → 2.41, GCC 12 → 14, OpenSSL 3.0 → 3.5, libgeos 3.11 → 3.13
   - GCC 14 turns some warnings into errors (`-Wincompatible-pointer-types`, 
implicit function declarations). This may affect sdist-only dependencies that 
are compiled at image build time or at worker startup.
   - Several Debian library packages were renamed or bumped in version (time_t 
64-bit transition, SONAME bumps). Custom images that extend the Beam image and 
`apt-get install` specific package names may need updates.
   
   **Preliminary validation (local, arm64, py312)**
   - `python:3.11`–`3.14-trixie` are available for amd64 and arm64.
   - `./gradlew :sdks:python:container:py312:docker` builds successfully.
   - Beam Cython extensions compile with GCC 14. `pip check` is clean, the upb 
protobuf check passes, and `ensurepip`, the `boot` launcher and `gcloud` work.
   
   **Remaining**
   - Build the py311, py313 and py314 images, plus the ML, distroless and 
expansion-service images, on amd64 and arm64.
   - Run the PostCommit Python ValidatesContainer (Dataflow and ARM), Python 
Xlang, ML inference and Azure ITs.
   
   
   ### Issue Priority
   
   Priority: 1 (urgent / mostly reserved for critical bugs)
   
   ### Issue Components
   
   - [x] Component: Python SDK
   - [ ] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [ ] Component: IO connector
   - [ ] Component: Beam YAML
   - [ ] Component: Beam examples
   - [ ] Component: Beam playground
   - [ ] Component: Beam katas
   - [ ] Component: Website
   - [ ] Component: Infrastructure
   - [ ] Component: Spark Runner
   - [ ] Component: Flink Runner
   - [ ] Component: Prism Runner
   - [ ] Component: Hazelcast Jet Runner
   - [ ] Component: Google Cloud Dataflow Runner


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to