fix(SUPP-28): bump testcontainers 1.20.4 → 1.21.4 for Docker 25+ compat #29
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
iterative-works/support!29
Loading…
Reference in a new issue
No description provided.
Delete branch "SUPP-28"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
org.testcontainers:{testcontainers,postgresql,mysql}from1.20.4to1.21.4(3-linebuild.millchange).1.32inDockerClientProviderStrategy.getClientForConfig; modern engines reject1.32(min1.44).testcontainers-java 1.21.4(2025-12-15) is the upstream backport — release notes: "This release makes version 1.21.x works with recent Docker Engine changes." NoforkArgs/-Dapi.versionoverride needed.Why this fix (not a Mill
TestModulemixin)The issue originally proposed a Mill
TestModulemixin to pin-Dapi.version=1.46viaforkArgs. Reviewing the upstream landscape revealed that testcontainers had already shipped a fix in1.21.4(and2.0.3), so the workaround is unnecessary. Seeproject-management/issues/SUPP-28/analysis.mdfor the original analysis and the prepended## Resolutionblock explaining why the workaround was superseded.Verification
Run against Docker engine
29.1.3(API1.52, min1.44):sqldb-postgresql.testpostgres:17-alpinestartedUser-Agent: tc-java/1.21.4, requests on/v1.44/containers/...sqldb-mysql.testmysql:8.0startedFull repo
./mill __.testgreen via pre-push hook.Upstream context
2.0.3+/1.21.4carries the fixTest plan
./mill sqldb-postgresql.testpasses on Docker 29.1.3 with real containers (no silent skips)./mill sqldb-mysql.testpasses on Docker 29.1.3 with real containers (no silent skips)./mill __.testgreen (pre-push hook)mainmergeCloses #28
🤖 Generated with Claude Code