docker-outside-of-docker: cannot install docker-compose

[hlecnt]

Hello,

I'm facing the issue just now. This is due to an incoming release of compose just now: the tag has been created but not the related release (github release) yet.

Thus the install.sh script found a tag version but without a corresponding release => it can't download the asset (not yet release) then fails.

The solution for now is to specify an already existing version like this:

        "ghcr.io/devcontainers/features/docker-outside-of-docker:1": {
            "dockerDashComposeVersion": "v2.32.3"
        }, 

Perhaps, a more robust way to handle this would be to to look at the available releases instead of tags (if allowed by the github API).

[bryanlittlefield]

Our team is also running into issues creating a new Codespace's using docker-outside-of-docker. We saw this same issue back in October of last year and we were able to patch it by using the method @hlecnt mentioned above ✅

Here are the errors we are getting back from the Creation Log:

9.841 compose_version=2.32.4
9.841 (*) Installing docker-compose 2.32.4...
9.929 curl: (22) The requested URL returned error: 404
9.931 Error: Failed to install docker-compose v2.32.4
9.932 chmod: cannot access '/usr/local/bin/docker-compose': No such file or directory
9.932 ERROR: Feature "Docker (docker-outside-of-docker)" (ghcr.io/devcontainers/features/docker-outside-of-docker) failed to install! Look at the documentation at ********/devcontainers/features/tree/main/src/docker-outside-of-docker for help troubleshooting this error.

[BenjaminBenetti]

Also facing this issue. Thanks @hlecnt you saved my bacon 🥓 with your workaround 😄

[xec-abailey]

Yep we are hitting this, the workaround above works fine. Thanks @hlecnt

[gauravsaini04]

Hi,
A PR has been raised for correcting this scenario where upon failure to install the latest release, it chooses a previous version to install instead of the latest..

PR #1252