[v0.21 backport] vendor: docker, docker/cli v28.0.0-rc.1 #2996
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.
We don't usually ship unstable releases, that's why Docker 28 RC bump on master got reverted before making our first RC:
But as discussed internally, Compose needs new network-related features from Docker 28 (cc @ndeloof @glours @thaJeztah). And because the Docker API have signature changes, Compose would not be able to vendor Docker 28.0.0-rc.1 with Buildx 0.21.0 as we are using the latest Docker 27.5.1 stable in current RC: https://github.com/docker/buildx/blob/v0.21.0-rc2/go.mod#L22
Compose could just vendor Buildx master but if patches are released in 0.21 branch, Compose might need to rely on it and would therefore be in broken state with vendoring. I don't think we have other choice than vendoring Docker 28 RC for this Buildx release.