Use debian-based builder image for bulding Linux glibc images #228
+37
−18
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.
Since the official node:{version} docker images are built on debian images, it makes sense to stick to those. This also helps ensure compatibility as the agent glibc versions may change, but using a docker image to build it keeps things as we expect.
Later on, when bullseye goes EOL, we can transition those builds to bookworm as well (and so on and so forth to the next versions). We get Ubuntu LTS builds ensured to be correct if we build on Debian, and I'm also adding some post-install tests to make sure that we can build successfully on the listed targets too.
Note that node v23 isn't supported in bullseye -- we never supported it as the agents were already 22.04 when we started supporting it. I've documented it in the README.
Successful build using this change: https://semaphore.ci.confluent.io/workflows/9c1a32e0-2e99-4f33-814f-8469dba04760?pipeline_id=26681b55-8aad-4564-9b3a-ecb1334a8389 (some flaky failure of promisified tests). I will remove the "Change version for testing" commit after review.
Fixes #221