Fix docker-compose install: bump to v2.29.7 for Docker API 1.44+ compatibility - #4592
Merged
Conversation
…atibility
Problem:
verify_docker_compose_wordpress_app (and other docker-compose tests) fail with:
The DockerCompose tool hardcoded the standalone binary v2.14.2 (Dec 2022), which negotiates Docker API 1.42. Newer Docker Engine builds (v25+) dropped support for API < 1.44, so the pinned client is rejected before any container is created.
Root Cause:
Stale version pin in docker_compose.py:55-59. All install paths (Redhat, CBLMariner, generic Posix fallback) route through _install_from_source(), so every affected distro hit the failure.
Change:
Bumped docker-compose from v2.14.2 → v2.29.7 (negotiates API ≥ 1.44).
Updated the release asset name from docker-compose-Linux-{hardware} → docker-compose-linux-{hardware} (Compose v2 renamed the asset to lowercase linux; the old capitalized path 404s on the new release).
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the DockerCompose tool’s pinned docker-compose standalone binary to a newer release so docker-compose-based LISA tests can run against newer Docker Engine versions (API 1.44+), and fixes the GitHub release asset name casing change.
Changes:
- Bump pinned docker-compose release from
v2.14.2tov2.29.7. - Update the downloaded release asset name from
docker-compose-Linux-{hardware}todocker-compose-linux-{hardware}.
✅ AI Test Selection — PASSED1 test case(s) selected (view run) Marketplace image: canonical 0001-com-ubuntu-server-jammy 22_04-lts-gen2 latest
Test case details
|
Collaborator
|
@SRIKKANTH Please run it against an older image to verify compatibility. |
Collaborator
|
I have run it against canonical 0001-com-ubuntu-server-jammy 22_04-lts-gen2 22.04.202403280 successfully. |
LiliDeng
approved these changes
Jul 14, 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
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.
Problem:
verify_docker_compose_wordpress_app (and other docker-compose tests) fail with:
Root Cause:
Stale version pin in docker_compose.py:55-59. All install paths (Redhat, CBLMariner, generic Posix fallback) route through _install_from_source(), so every affected distro hit the failure.
Change:
Bumped docker-compose from v2.14.2 → v2.29.7 (negotiates API ≥ 1.44).
Updated the release asset name from docker-compose-Linux-{hardware} → docker-compose-linux-{hardware} (Compose v2 renamed the asset to lowercase linux; the old capitalized path 404s on the new release).
Description
Related Issue
Type of Change
Checklist
Test Validation
Key Test Cases:
Impacted LISA Features:
Tested Azure Marketplace Images:
Test Results