Skip to content

Installed docker-compose too old with new Docker version release 29.0.0 #807

@addy90

Description

@addy90

Dear BBB-Team,

on my BBB install, Docker has been updated to version 29.0.0.
In it's release notes, it states "The daemon now requires API version v1.44 or later (Docker v25.0+)."

During running of the bbb-install script on BBB 3.0 the following error appears:

docker-compose -f /root/greenlight-v3/docker-compose.yml up -d
ERROR: client version 1.25 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version

As such, updating, installing, starting or stopping of Greenlight does no longer work.

The custom docker-compose version 1.24.0 that is installed seems to be too old now. Current version is 2.40.3 (and is automatically shipped with the Docker install).

I am, however, not entirely sure which docker-compose versions support which Docker API versions. I could not find a reference table for this issue.

Maybe it is best to completely avoid the custom and older docker-compose command, since docker compose (built in) also exists by default.

When I run docker compose (instead of docker-compose) manually, Greenlight comes back online, although with a warning concerning the version number, as explained in the official docs.

# docker compose -f /root/greenlight-v3/docker-compose.yml up -d
WARN[0000] /root/greenlight-v3/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Running 4/4
 ✔ Network greenlight-v3_default  Created                                                                                                              0.0s
 ✔ Container postgres             Started                                                                                                              0.3s
 ✔ Container redis                Started                                                                                                              0.4s
 ✔ Container greenlight-v3        Started  

Thanks for your support and keep up the great work!
Best regards!

EDIT: There is now a Blog post about this particular issue on Docker with additional workarounds:
https://www.docker.com/blog/docker-engine-version-29/#minimum-api-version-update

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions