Pin docker-ce-cli to version 24.0.x for API 1.43 compatibility in k8s-ci-builder #4185
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 type of PR is this?
/kind bug
What this PR does / why we need it:
This PR pins
docker-ce-clito version 24.0.x in the k8s-ci-builder image to ensure API version 1.43 compatibility with Docker-in-Docker in CI environments.While
docker-cewas already pinned to 24.0.x, thedocker-cepackage has an unversioned dependency ondocker-ce-cli. This allows APT to install the latest availabledocker-ce-cli(currently 29.0.0 with API 1.52), which is incompatible with the DinD setup that only supports API 1.43.Which issue(s) this PR fixes:
Follow-up to #4183
Special notes for your reviewer:
This is the same fix as #4183, but applied to the k8s-ci-builder image instead of k8s-cloud-builder. The k8s-ci-builder image installs
docker-ce(full daemon) while k8s-cloud-builder only installsdocker-ce-cli, but both suffer from the same issue where the CLI can be upgraded to an incompatible version.Does this PR introduce a user-facing change?