Skip to content
This repository was archived by the owner on Jun 16, 2026. It is now read-only.

build: pin envoy-build-ubuntu to upstream v1.38.2 image#9

Merged
cybercyst merged 1 commit into
mainfrom
ci/build-image-v1.38.2
Jun 15, 2026
Merged

build: pin envoy-build-ubuntu to upstream v1.38.2 image#9
cybercyst merged 1 commit into
mainfrom
ci/build-image-v1.38.2

Conversation

@cybercyst

Copy link
Copy Markdown
Member

Problem

The build stage in Dockerfile compiles Envoy from source (./ci/do_ci.sh release.server_only) inside the envoyproxy/envoy-build-ubuntu toolchain image. That image must match the build image upstream uses for the release we ship (v1.38.2).

It was pinned to tag f4a881a1205e8e6db1a57162faf3df7aed88eae8 (digest sha256:b10346fe…), which does not correspond to any 1.38.x release.

Verification

The authoritative source is the build-image.tag field in upstream envoyproxy/envoy .github/config.yml (the image is tagged by git SHA; the sha: fields are content digests used for verification). Checked across the 1.38.x line:

Upstream ref build-image.tag
v1.38.0 86873047235e9b8232df989a5999b9bebf9db69c
v1.38.1 86873047235e9b8232df989a5999b9bebf9db69c
v1.38.2 86873047235e9b8232df989a5999b9bebf9db69c

Change

Repin to upstream v1.38.2's build image:

  • tag 86873047235e9b8232df989a5999b9bebf9db69c
  • digest sha256:1b3c82ca34c505c4951918b2e0a0c3db88cf266ebbf4196e4b0fba8fa137ada3 (multi-arch: amd64, arm64)

🤖 Generated with Claude Code

The build stage compiles envoy from source via do_ci.sh inside the
envoy-build-ubuntu toolchain image, so it must match the build image
upstream uses for the release we ship (v1.38.2).

The Dockerfile pinned tag f4a881a1 (digest b10346fe), which does not
correspond to any 1.38.x release. Upstream v1.38.0/1/2 all use build
tag 86873047 (per .github/config.yml build-image.tag). Repin to that
tag and its multi-arch digest 1b3c82ca so we build with the correct
toolchain.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant