fix(packaging): install s3cmd via apt to fix k6packager image build - #5953
Merged
Conversation
Contributor
Author
|
This isn't needed for v2.0.0 as there is a working k6packager - the v2.0.0-rc1 was build with that image, while this was failing in the background. |
mstoykov
temporarily deployed
to
azure-trusted-signing
May 9, 2026 06:52 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
mstoykov
temporarily deployed
to
azure-trusted-signing
May 9, 2026 06:54 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
The packager Docker image build started failing after the base image was updated to debian:trixie, which ships Python 3.13 and enforces PEP 668. `pip3 install s3cmd==2.4.0` is now refused with "externally-managed-environment". Trixie packages s3cmd 2.4.0-3, so install it via apt and drop the no-longer-needed python3-pip dependency.
mstoykov
force-pushed
the
feature/fix-k6packager
branch
from
May 9, 2026 07:08
458bd58 to
6eb3efa
Compare
mstoykov
temporarily deployed
to
azure-trusted-signing
May 9, 2026 07:14 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
mstoykov
temporarily deployed
to
azure-trusted-signing
May 9, 2026 07:15 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
szkiba
approved these changes
May 11, 2026
oleiade
approved these changes
Jun 8, 2026
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
3 participants
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.
What?
In
packaging/Dockerfile, installs3cmdfrom the Debian repository insteadof via
pip3, and drop the now-unnecessarypython3-pipdependency.Why?
The
k6packagerworkflow has been failing since the base image was bumped todebian:trixie. Trixie ships Python 3.13, which enforces PEP 668, sopip3 install s3cmd==2.4.0is rejected witherror: externally-managed-environment.Debian trixie packages
s3cmd 2.4.0-3— the same upstream version previouslypinned via pip — so installing it through
aptkeeps the version constant andsidesteps PEP 668.
Failing run for reference:
https://github.com/grafana/k6/actions/runs/25266283376/job/74081274422
Locally verified:
s3cmd --versionin the resulting image reports2.4.0.Checklist
make check) and all pass.Checklist: Documentation (only for k6 maintainers and if relevant)
Related PR(s)/Issue(s)