Fix: update EOL base images and broken configs in four community builders#714
Open
64johnlee wants to merge 1 commit into
Open
Conversation
**jsonnet**: ubuntu:xenial (EOL Apr 2021) → ubuntu:22.04 LTS - Also adds --no-install-recommends and explicit cache cleanup **earthly**: ubuntu:bionic (EOL Apr 2023) → ubuntu:22.04 LTS; version 0.5.23 → 0.8.0 - 0.5.x is over two major versions behind; 0.8.x is the current stable series **protoc**: debian:buster-slim (EOL Sep 2024) → debian:bookworm-slim (current stable) - Default protobuf version 3.12.4 → 27.3 (current stable release) - Note: protobuf adopted sequential versioning after v3.21; 27.3 is the correct format **dataflow-python3**: three bugs fixed 1. python:3.7 (EOL Jun 2023) → python:3.12 (LTS through Oct 2028) 2. ENTRYPOINT bin/bash → ENTRYPOINT ["/bin/bash"] (exec form required for signal handling) 3. Removed broken virtualenv pattern: `source venv/bin/activate` inside RUN has no effect on subsequent layers. Each Docker RUN starts a fresh shell, so activated environments are discarded. Direct pip install into the image is correct. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
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.
Summary
Fixes four community builders that use end-of-life base images or have broken configurations that prevent them from working correctly.
jsonnet — ubuntu:xenial EOL (Apr 2021)
File:
jsonnet/Dockerfileubuntu:xenialreached EOL on April 30, 2021. It no longer receives security patches.ubuntu:22.04LTS (supported until April 2027).--no-install-recommendsand cache cleanup to reduce image size.earthly — ubuntu:bionic EOL (Apr 2023) + stale version
File:
earthly/Dockerfileubuntu:bionicreached EOL on April 2, 2023.ubuntu:22.04LTS.0.5.23→0.8.0(0.5.x is two major versions behind; 0.8.x is current stable).protoc — debian:buster-slim EOL (Sep 2024) + stale version
File:
protoc/Dockerfiledebian:buster-slimreached EOL on September 10, 2024.debian:bookworm-slim(current Debian stable, supported until 2028).3.12.4→27.3(current stable; protobuf adopted sequential versioning after v3.21).dataflow-python3 — three bugs fixed
File:
dataflow-python3/Dockerfile1. Python 3.7 EOL (Jun 2023) → Python 3.12
Python 3.7 no longer receives security updates. Python 3.12 is LTS through October 2028.
2. Broken ENTRYPOINT format
3. No-op virtualenv activation (3 broken RUN layers)
Each Docker
RUNexecutes in a fresh shell;source venv/bin/activatehas no effect on subsequentRUNcommands. The pip install was going to the system Python, not the virtualenv. Also,ENTRYPOINTwas placed betweenRUNcommands which is invalid.🤖 Generated with Claude Code